RE: Release Branches / 3-plus Development Streams
From: Oefelein, Martina <Martina.Oefelein_at_dionex.com>
Date: 2007-04-10 18:01:17 CEST
Hi Chuck,
Like you, we have to maintain 3 existing releases concurrently with the trunk. We develop (usually) in the trunk and merge fixes (and sometimes features) to the release branches. If I understand you correctly, you are merging in the other direction, from the oldest release branch to the newer branches and finally to the trunk.
I think both ways will work technically, and the choice is probably more a question of development philosophy and procedures.
ciao
-----Original Message-----
We have lately adopted SVN as our standard source code mgt tool.
Previously, we used CVS and had a standard approach to branching in the
For this situation, our branching model using CVS was basically to
/---------------------
We would then merge from R1 to R2, from R2 to R3, etc. Eventually, R
So, here's my question, so we don't go down the wrong track, can any of
Chuck Irvine
---------------------------------------------------------------------
---------------------------------------------------------------------
|
This is an archived mail posted to the Subversion Users mailing list.
This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.