[ruby-core:21075] Re: Happy new year and... moving Ruby development to Git?

mathew wrote:
> My opinion:
> 
> Git is currently the flavor of the month. It's getting adopted for 
> reasons which amount to fashion rather than legitimate technical merit. 
> It has a horrible user interface, and a fundamentally broken model.

I'm not as negative about git, since for my limited scm-fu hg and git 
are just svn with a local repo, but I definitely agree with the "flavor" 
statement. Between minor versions git has changed command-line options, 
added and removed commands, and introduced bugs. Don't get me wrong, I 
like it, but I don't like it enough to go through the pain of moving an 
existing large project to it without a very good reason. Add to that 
what Matz said about wider tool support and it's really not compelling.

JRuby will probably be making a move to Mercurial soon, and our reason 
for doing so is that we're moving to the JRuby-on-Rails-based kenai.com 
project-hosting site Sun built over the past couple years. If we're 
moving there, we'll need to migrate SCM anyway, so we might as well 
migrate to DSCM. Hg is the current likely candidate simply because it's 
well supported by kenai and by the tools we use (namely, NetBeans).

An official up-to-the-hour git mirror would probably be the nicest way 
to support git for ruby-core right now, and I think github even supports 
git-svn clones in a smart way now. I run off a copy of Vladimir's 
git-svn mirror myself, and I use git-svn for JRuby work, so that would 
be my recommendation, at least until git support is rock solid and 
relatively consistent across all the usual platforms and tools.

- Charlie