Would you migrate from cvs to svn or directly to git or hg?

Question

I don\'t know if this is the right forum to ask.

My company makes use of CVS as a version control system. We plan to move to a more modern version control system. What w

Answer 1

1. Merging code and resolving conflicts is easier using a distributed VCS like GIT or Mercurial. The reason is that GIT or mercurial have all the intermediate snapshots of the two "end codes" to be merged while subversion would only know the end snapshot unless each SVN user is working in his/her own branch.

2. With a distributed VCS, you are not dependent on the network to check code in.

3. If you have a large number of users checking stuff into VCS on a daily basis, your SVN server better be very powerful to handle concurrent check-ins/outs. DVCSs dont have that problem.

We made our switch from CVS to SVN and now to Mercurial and we are very happy with the transition. There is nothing about SVN we are missing in Mercurial but going back to SVN would be painful.