Reviewing this thread, it seems everyone is pretty much in favor of this. I propose we proceed by electing a "git transition advisor"... someone who:
1) is sufficiently knowledgeable with git to identify roadblocks during the transition and is willing to make it a point to propose and follow through with solutions, 2) can serve as the main point of contact with INFRA tickets related to the transition, 3) can advise other developers on best practices for things like when to branch, where to put contribs, when to delete a branch (if ever), etc. for things related to the shared repo. Item 3 is really something we can all do to the extent that our expertise allows, but it'd be nice to have somebody willing to do item 2, in the context of their experience in item 1. I would like to nominate Josh Elser, because I think he's qualified, and because his exact response to this inquiry was "Yay, git." -- Christopher L Tubbs II http://gravatar.com/ctubbsii On Tue, May 21, 2013 at 5:44 PM, Christopher <ctubb...@apache.org> wrote: > I'm sure this has been entertained before, I'm starting to think that > we should seriously consider switching to git, maybe sooner (during > 1.6 development cycle?). > > -- > Christopher L Tubbs II > http://gravatar.com/ctubbsii
