stable trunk vs unstable trunk branching strategy
Hi, What are the pros and cons of stable trunk strategy (day to day commits on release branch, merge to trunk after production release) vs unstable trunk stategy (day to day commits on trunk, cut a branch when ready for release). We have monthly release cycles and frequent emergency bug fixes there after. The emergency bug fixes sometimes can be multiple times during a day. There are about 10-15 developers for each project. Can you provide examples of branching strategy and the release workflow you follow. Thanks
Hi, The best thing I could do really is link you to discussions on this subject - there's plenty online and some good advice on strategies in the svn book as well here: http://svnbook.red-bean.com/en/1.7/svn.branchmerge.commonpatterns.html A video here discusses alternatives: http://www.slideshare.net/cb372/branching-strategies Some ideas on when to branch and merge here: http://lostechies.com/derickbailey/2010/02/24/branching-strategies-when-to-branch-and-merge/ Hope that gets you started, you're best doing what fits your team and your own ways of working as that'll be much easier and quicker to put in place than completely restructuring established practices. Good luck with it all :)
We have monthly release cycles and frequent emergency bug fixes there after. The emergency bug fixes sometimes can be multiple times during a day. There are about 10-15 developers for each project. _________________ Cut down your exam stress by using our latest e six sigma and high quality gmat and We provide updated rc.edu with 100% pass guarantee along with Boston College
1-3 of 3
Reply to this discussion
You cannot edit posts or make replies: You should be logged in before you can post.