When to Branch in Subversion
Posted on 2010-08-27
We are a small group, just 3 developers, working on separate parts of the code base. I'm proposing to check all changes into the main Subversion trunk. After a release, we can tag the code in case there are any fixes needed to the release, and then begin developing and checking code into the main trunk.
There is a counter argument that all new work should be done in a branch. I've never heard of working like this.
Is there any reason not to prefer my approach and make all changes to the main trunk.