Concurrent Release Branch Development

[C. Michael Pilato]

On 12/21/2010 11:39 PM, G. Eric Babcock wrote:
> We consistently work concurrently on multiple Release Branches (*Chapter 4.
> Branching and Merging
> <http://svnbook.red-bean.com/nightly/en/svn.branchmerge.commonpatterns.html#svn.branchmerge.commonpatterns.release>*). 
> A big problem is the failure to 'forward fit' changes from older release
> branches into newer release branches.  I read how we could manually
> 'remember' and merge older release branches into newer release branches -
> but we need to systematically ensure this is done, or in rare cases
> consciously not done.  I suppose there is a corollary condition of removing
> changes from newer release branches when they are reverted from older
> branches, or ensuring there was a conscious decision to to not remove them.
> 
> Is there any discussion on how to manage this with subversion?

The book probably doesn't cover this material.  I'd recommend inquiring at
users at subversion.apache.org.

-- 
C. Michael Pilato <cmpilato at red-bean.com> | http://cmpilato.blogspot.com/