(cross-posted to Twitter to ensure a fragmented conversation)
We’re likely to make the move from SVN to Mercurial or Git in the next few months, for at least a segment of our development at Crowd Favorite.
I’ve been doing a bit of reading on pros and cons, but would appreciate real-world experience from folks that have it. In particular with a focus on many projects sharing libraries as externals and being worked on in a team environment.
Being able to stick code we Open Source on Google Code would be nice with Mercurial, however Github seems like a pretty stable alternative.
This post is part of the thread: Version Control – an ongoing story on this site. View the thread timeline for more context on this post.
Google Code also has a nice article on how to import Git into project hosting: http://code.google.c[...]rtingFromGit
But if the choice is between Google Code and Github… well… easy choice (Github).
Can I ask a stupid question:
Why are you making the change in the first place?
I guess I just am not grasping the magical pixie dust that these other VC systems have over SVN.
One of the big things is supposed to be the distributed/serverless nature of them, but yet the projects always seem to revolve around putting the code into github or some other central repository. Huh? how is that different?
Yes, running external libraries with SVN can be a pain, but what else with SVN isn’t working for you?
My -2 pfennig.
3 reasons off the top of my head:
1 local commits
2 better branch/merge support
3 developers like using the latest and greatest tools
Besides that, what have the Romans ever done for us?
Git.
I experimented heavily with both before I comitted to git, and for better or for worse git is the more popular tool (where more popular involves having a more robust communities and a more robust ecosystem with better tools which is very important to me)
Using it for just about everything these days.
/etc on my servers, in git.
dns zone files, in git.
<3 it!
I myself use GIT and have never tried Mercurial, but I simply love GIT, flexible, easy to use once you get how it works.