Top Rated CVS Alternatives
CVS is very simple and sophisticated version control. It’s is good version control system. Review collected by and hosted on G2.com.
Pricing for enterprises is very costly compare to other version control systems Review collected by and hosted on G2.com.
12 out of 13 Total Reviews for CVS

CVS is a simple tool for code commit which uses command line interface. Review collected by and hosted on G2.com.
If 2 or more developers work on same file and commit at same time then conflict occurs,This can be annoying. But automerge feature is available when repository is updated. Only those with conflict needs to be manually fixed and committed again. Review collected by and hosted on G2.com.
CVS is a version control system. Its simple and less complex and has even a good UI to make it easier. Its good for a beginner and probably if you have lesser number of developers in the team. Review collected by and hosted on G2.com.
Not possible to manage merges well. Doesnt have more advanced features Review collected by and hosted on G2.com.
CVS tool supports simple version control for multiple users on Unix ecosystem. It's easy to learn and pick up the nuances. It's powerful if used the right way. Review collected by and hosted on G2.com.
It's but pricey and clunky with merge resolutions. The community support sometimes seems to be not that great. Review collected by and hosted on G2.com.
I use a Unix distribution with Virtual Box on windows and use CVS on that to back up my C code. So far, CVS and Git have been my primary choices. The reason why I prefer CVS is that it's less processor intensive and integrates easily into my Unix system. It also helps backup my code so that I can back to a previous built if an unexpected error occurs. Also, there is a large community of users and open source code too. Review collected by and hosted on G2.com.
If I was using an actual Unix system and not a Virtual Box, I wouldn't use CVS. I would've used Git or Hg because they're simply more modern and faster. Review collected by and hosted on G2.com.
CVS was great when it first came out as it was one of the first software products to solve a very urgent need of versioning (no more copy-pasting files!) Review collected by and hosted on G2.com.
It's obsolete and there is literally zero reason to use it ever again. More modern version control systems (e.g. git, hg, etc) provide a huge superset of the features that CVS offered and there are tools to migrate CVS repos. If, for some strange reason, you can't migrate a CVS repo you can probably still find a tool to use git locally (e.g. I know there's a git-svn tool that uses git locally and then commits to SVN. There's likely a git-cvs or hg-cvs tool out there somewhere).
The huge wins of modern VCS' are distributed repos (you don't need a centralized server), and vastly superior branching & diffing. There are a million other improvements, but these are the largest 2 IMO. Review collected by and hosted on G2.com.

I have used CVS a couple of times throughout my career, and in fact, in one organization, I found that they had been using it for about 5 continuous years without any kind of problem or error, it is efficient when running and helps you maintain that high standard of software quality among multiple development groups. Review collected by and hosted on G2.com.
It can become quite complex at the beginning and you will probably need extensive knowledge of UNIX platforms. Review collected by and hosted on G2.com.
CVS uses delta compression ie. it will only push the changes from new version to the previous version on server. This will save a lot of time in case of huge files.
One can easily compare the two versions, checks the complete history (even if the file was deleted and then added again with the same name).
It allows check-in only in case you have the latest version of file, if some one has already added some changes after you check-out, it will show error and will not let you add to avoid overlapping/missing of changes. Review collected by and hosted on G2.com.
WIth so many other version control option in market, which have advanced features along with basic features cvs provides, its usage has been decreased. Review collected by and hosted on G2.com.
It's very common, easy to find help and pretty straightforward to use. It also does a decent job of merging changes and noting any conflicts. Review collected by and hosted on G2.com.
Some operations seem to take a lot of extra, unnecessary steps, such as adding or deleting files, or just checking out a few files that are in different subdirectories several folders deep. Review collected by and hosted on G2.com.

It is one of the most robust and stable source code version controllers on UNIX servers, with the advantage of having a long history. It can be very meticulous in configuring it and making it adapt to your team and development environment. Review collected by and hosted on G2.com.
It is complicated and somewhat old, usually to have the services running in good shape you need quite a few hours of configuration and really know what you are doing if you don't want to spend days trying to fix errors. Review collected by and hosted on G2.com.