Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 848
  • Last Modified:

When to Branch in Subversion

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.
0
jkavx
Asked:
jkavx
2 Solutions
 
chapmanjwCommented:
This chapter on branching and merging gives a good explanation as to why branching should be used: http://svnbook.red-bean.com/en/1.0/ch04s02.html 
0
 
Brad HoweDevOps ManagerCommented:
We use Collabnet in the office for my guys and this doc helps new Developers get the idea.
http://blogs.open.collab.net/svn/2007/11/branching-strat.html
What you are questioning sounds like the difference between and unstable vs agile branching system. With the unstable branch system daily builds would identifiy issues more quickly. While an agile approach makes it much more difficult with all the competely channels.
In the end, it depends on your SDLC and what methodologies your company employes.
Cheers,
Hades666
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now