Delightfully Wrong About Git
Posted:A very long time ago I mentioned on Twitter that I was looking at Git as a replacement for Subversion and Perforce with my personal projects, but lamented moving to Git at Slide would not be feasible
Back in April, after spending a week with projects like Tailor and git-svn(1) I started to look at the potential of moving just my team over to Git for evaluation purposes. By the end of May I had requested Git to be installed on the machines that we use for development on a day-to-day basis and we moved the team over to Git by the second week of June.
What followed were six months of sloshing uphill, some of the most notable milestones that we had to figure out in this time frame were:
- Whereas in the Subversion architecture with a central repository there is a very clear development focal point for sharing code between developers, what is this in the Git workflow?
- How do you ensure developers don't forget code was committed "in that one branch, in that one repository" and keep track of code
- How will Git integrate with Hudson, Trac and our other pieces of development infrastructure? (answered here)
At the end of the day, I'm pleased as punch with the transition. I don't hate Subversion, I just love Git; call me "spoiled" but I think we deserve something more than a system that strives to be "a better CVS".
Update: I've posted an addendum: Why we chose Git, a rebuttal