David Van Couvering wrote:
Interesting idea. I feel like I'm really missing something. If no
other changes go into the svn copy, why are we making the copy?
I guess the goal is to flip the beta flag in the copy.
Trunk would still be alpha as usual.
This would be approach 4) Other options, where the following cons are gone:
- The beta candidate says that it is alpha.
- The trunk says it is beta, which may be confusing.
Based on Andrews suggestion, the copy is "thrown away"/forgotten when
the time comes to create the real branch.
--
Kristian
David
Andrew McIntyre wrote:
On 8/9/06, Kathey Marsden <[EMAIL PROTECTED]> wrote:
I say this is not true. We make the branch and just make that one beta
flag flip.
Everyone gets their builds setup and running but we keep working on the
trunk.
Nobody bothers with merging fixes to the branch.
Then at whatever point we feel we need a real branch someone does one
biggish merge
with the range for all that has gone into the trunk so far and just
reverse merge the one change
for the 10.3 version bump.
There's another option, too, that I just thought of. svn copy the
trunk into tags/10.2.1.0_beta. Flip the beta flag, roll the beta
distributions. No other changes go into this copy of the trunk.
When the time comes, branch the new 10.2.1.0 branch off the trunk, and
do any reverse merging as necessary.
SVN copies are cheap, we should take advantage of that.
andrew
