|
Boost : |
From: Peter Dimov (pdimov_at_[hidden])
Date: 2001-12-19 08:45:56
From: "Beman Dawes" <bdawes_at_[hidden]>
> It has been suggested by several people that we do some form of a
> pre-release code freeze well-prior to the actual release. This will give
> us time to resolve regression test failures before the actual release.
>
> Two different CVS procedures were suggested for implementing the freeze:
>
> (1) At the freeze date, create a branch for the release. Apply fixes to
> that branch until satisfied. After the release, merge the branch back
into
> the main trunk.
>
> (2) At the freeze date, tag for release. Apply fixes to the main trunk
> (updating the tag) until satisfied. No post-release merge is required.
Why not simply announce a pre-release freeze, during which only bug fixes
are allowed to go into the CVS? No branching or tagging would be necessary.
-- Peter Dimov Multi Media Ltd.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk