From: Jeff Garland (jeff_at_[hidden])
Date: 2002-10-24 17:49:52
It seems to me that part of the release process that would delay merges
from the candidate branch to the main branch is misguided. Critical
changes made to the release branch should be immediately merged on the
main branch. This avoids the issues of forgetting to merge later
which can lead to lost fixes or fixes that are much harder to merge.
Also, I don't see where in the description of procedures there is an
indication to wait on merging back to the main branch. Finally,
in an informal poll of some boost developers it seems that most of
us are already doing immediate merges. I recommend we make this
the general release policy.
> -----Original Message-----
> From: boost-bounces_at_[hidden]
> [mailto:boost-bounces_at_[hidden]]On Behalf Of John Maddock
> Sent: Thursday, October 24, 2002 4:39 AM
> To: boost
> Subject: [boost] Another reminder to merge changes from the release
> It doesn't look as though the post release procedure is working to well: to
> recap it is the responsibility of anyone who made changes to the release
> branch to also make those changes on the main trunk.
> Since no one else has done it, I've just merged the changes in:
> I also tried to merge /index.htm but there were conflicts - can those
> responsible for the changes here please sort them out?
> There may also be unmerged changes in the headers, but to be honest I can't
> see any easy way of figuring out whether this is the case.
> John Maddock
> Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk