DCVS is based on CVS and therefore benefits from all advantages of CVS:
- CVS is stable
- CVS is approved
- all of CVS's strengths and weaknesses are known
Thus, integrating DCVS in your development environment poses no unpredictable risks.
CVS and DCVS are
- integrated in various IDEs and GUIs
- available on almost all development platforms
DCVS and CVS
- use the security infrastructure of their operating system
- use cryptographic hash for access control through application of SSH.
- provide a simple and intuitive user interface
and almost anywhere
- commercial support for CVS is available
The Migration from CVS to DCVS requires minimum efforts
- The migration path from CVS to DCVS ist very simple
- Training is obsolete, as experienced CVS users can also handle DCVS.
Snapshots and Change Sets provide better support for release engineering and process management
New in DCVS: The functionalities snapshot and change set support a controlled release management.
The Unix manual page, section 1 user command dcvs contains a paragraph about the use of change sets and snapshots in dcvs. Here you find the description of the regular use cases.
Simple and quick installation
Even non-CVS-users can easily and quickly install DCVS. DCVS installation on three sites in 30 minutes describes step by step how you have to proceed.
http://www.elegosoft.com/dcvs/doc/DCVS_IN_30_MINUTES
DCVS is an open source project
The DCVS code is freely distributable under the GNU and BSD style licenses. Thus, acquiring DCVS is free of charge and licence bureaucracy.
