Solved

When to Branch in Subversion

Posted on 2010-08-27
2
829 Views
Last Modified: 2013-11-25
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
Comment
Question by:jkavx
2 Comments
 
LVL 21

Accepted Solution

by:
chapmanjw earned 250 total points
Comment Utility
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
 
LVL 30

Assisted Solution

by:Brad Howe
Brad Howe earned 250 total points
Comment Utility
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

Featured Post

IT, Stop Being Called Into Every Meeting

Highfive is so simple that setting up every meeting room takes just minutes and every employee will be able to start or join a call from any room with ease. Never be called into a meeting just to get it started again. This is how video conferencing should work!

Join & Write a Comment

Cobalt Digital Marketing began using the Scrum Framework development process in summer 2009.  We hired a consultant to train the teams, observe meetings, and answer questions. He recommended that we begin using one-week sprints for several reason…
"Disruption" is the most feared word for C-level executives these days. They agonize over their industry being disturbed by another player - most likely by startups.
This demo shows you how to set up the containerized NetScaler CPX with NetScaler Management and Analytics System in a non-routable Mesos/Marathon environment for use with Micro-Services applications.
When you create an app prototype with Adobe XD, you can insert system screens -- sharing or Control Center, for example -- with just a few clicks. This video shows you how. You can take the full course on Experts Exchange at http://bit.ly/XDcourse.

763 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

11 Experts available now in Live!

Get 1:1 Help Now