I think it is a mistake trying to persuade a large team to change SCM system without them having a compelling reason to make that switch.
I think git is great. I use it all the time and can't imagine working without it. However, most programmers I've encountered want to write programs more than they want to interact with an SCM system. They want their SCM system to act like a simple version controlled file system which is fast enough to not annoy them and which otherwise stays out of their way. We switched a large team to git a few years ago. I think git is great, but there are down sides to making a large organizational change, and source control change is a large organizational change. Refer to http://j.mp/switched-to-git for that blog posting. Another blog http://codeascraft.etsy.com/2011/12/02/moving-from-svn-to-git-in-1000-easy-steps/ Mark Waite >________________________________ > From: Andrew Gray <andrew.paul.g...@gmail.com> >To: jenkinsci-...@googlegroups.com; jenkinsci-users@googlegroups.com >Sent: Wednesday, March 7, 2012 6:44 PM >Subject: Git vs SVN > > >Hi All, > >At one client site we are using SVN. Client is a big corporate with projects >teams spread across 3 buildings on the same site. Project teams are often >sitting next to each other. > >I am trying to convince collegues that we should move to GIT. I have sent >them all the usual "GIT vs SVN" and "Why GIT is better than SVN" URLs. > >The pushback I am getting is: >1. What does GIT give me that I don't get with SVN >2. It is just another thing I have to learn and why should I when I don't know >what benefit I get. > >Can anyone assist with providing a compelling reason to move to GIT. > >Regards, > >Andrew > > >
