On Fri, Aug 21, 2009 at 11:14 AM, Marcelo de Moraes Serpa<celose...@gmail.com> wrote: > > I'm using git, actually I love git. However, we started with svn > unfortunately and only now the management saw the benefits of git and > we migrated. However, 99% of the developers of this project does not > know how to use git, and with this I mean they don't know what > branches are actually and how they work. The investment of time to > teach them this would ruin this project, which is already behind the > schedule.
Sounds like you have a risk assessment decision to make. You are *already* introducing changes to a late project: you moved to Git, you're trying to implement CI, you're talking about version control policy. Given that -- which is more likely to pose a greater threat to your delivery schedule? 1.) Taking an hour for a mandatory lunch-and-learn, buying everyone pizza, and saying "Listen up folks. We're about to introduce our friends 'git checkout -b' and 'git merge', and then I'm going to tell you the version control policies, and you _will_ follow them or you get to be the one who babysits the continuous integration server." (Really, you _can_ explain Git branching in a few minutes. Hell, just show everyone the Peepcode screencast.) 2.) Stopping short of introducing changes that are responsive to the changes you've already made, and allowing people to continue the development practices that made your project late -- only now with tools they're unfamiliar with and using badly. I really don't think the answer to this is automatic. Sometimes #2 _is_ the right answer. But if that's the case, you should probably also abandon any attempt to maintain continuous integration policies. What you've just said then is that this is the wrong time to make things better. So stop. Don't make any decisions, don't change anything. And make sure you're out of the blame path for the project's schedule. > Or maybe we should just use branches, but won't be easy to convince > the management to do this now. Question for you: is "management" committing code? If not, why should you need to convince them of anything? Don't ask permission. Branching doesn't need any extra budget. Just start doing it. Follow good practices, and let your teammates know what you're doing and why. You guys are there to do your jobs. Management's job is to empower you to do so. If this is the sort of company where you have to raise your hand every time you need to go to the bathroom, then you have issues a continuous integration server won't solve. -- Have Fun, Steve Eley (sfe...@gmail.com) ESCAPE POD - The Science Fiction Podcast Magazine http://www.escapepod.org _______________________________________________ rspec-users mailing list rspec-users@rubyforge.org http://rubyforge.org/mailman/listinfo/rspec-users
