From: John Maddock (john_at_[hidden])
Date: 2008-08-21 04:58:25
Stefan Seefeld wrote:
> In fact, what is trunk good for ?
> My current understanding of the situation suggests to me that I should
> just never commit anything to trunk, but the current 'release branch'.
> That way I only have to care about a single check-in (that's what I'm
> used to on other projects). Of course, as soon as a significant amount
> of people do that, trunk becomes useless.
> I see a couple of other issues with this procedure as I understand it
> (now), but this is not the point and place to discuss them.
There should never *ever* be any changes applied to the release branch that
have not been applied and tested on Trunk *first*.
In short: commit to trunk, wait for the test results to cycle at least once,
and when you're sure that the code is stable and release ready on all
supported platforms, only then merge to the release branch. The expectation
is that most people will merge to the release branch only periodically, when
there are a number of release-ready changes pending.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk