SVN vs VSS vs CVS Comparing HELP
cvs, svn, version-control, visual-sourcesafe
Solution
SVN versus CVS is simple. SVN was developed as a new Software to be used instead of CVS to correct some issues with CVS.
One issue I know is the problem with moving and renaming files inside the repository. This is a big issue if you tend to refactor a lot in your codebase.
More is found here: Limitations of CVS on Wikipedia. And here: Criticism on VSS on Wikipedia And for comparisons: Limitations of SVN on Wikipedia
Problem
We are currently determining if we would move CVS and VSS projects to a single SVN server. I've been using SVN for a long time now but is forced to use CVS and VSS for work stuff. Would you please help me give reasons why moving to SVN would be better than buying a VSS 2005? And also what the benefits of moving from CVS to SVN would be? We have projects in C#.NET/Java/Perl/Visual Basic. Beyond the cost difference what more can i say to the bosses to convince them to move to svn. And is there a way to preserve the histories of the VSS and CVS when moving to SVN?