Branching per feature
If you’re working in an Agile environment, chances are you’re working from a continuously integrated source control system, with a trunk, branches etc… If that’s the case many people will be familiar with “the build” being broken (typically the trunk) which can bring development (and sometimes testing) to a grinding halt. The larger the team(s) the more likely this is. I’ve recently been giving thought to branching per feature. The concept isn’t quite ready yet, but I thought I’d share my ideas and see if anyone can add to them (or shoot them down).
Git, an Alternative to Subversion?
One of the guys at work (Jimmy Tight Pants) suggested looking at Git as a replacement to Subversion having recently been playing around with Rails. Sort of in conflict, and in interest to the suggestion I thought I’d try out switching my personal subversion repository across to Git. Also I liked the chance of having a source control system called “git” (I pronounce it git instead of “jit”).
Firstly, I won’t explain too much about Git and who uses it. It’s easier just to pop to the website to read more about Git.