Boost logo

Boost :

From: David Abrahams (david.abrahams_at_[hidden])
Date: 2001-12-19 08:57:14


----- Original Message -----
From: "Beman Dawes" <bdawes_at_[hidden]>
To: <boost_at_[hidden]>
Sent: Wednesday, December 19, 2001 8:42 AM
Subject: [boost] Which CVS release procedure?

> 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.

With procedure 2 it seems to me that there's no point tagging until the
actual release goes out. You still need to rely on people to keep major
changes off the main trunk.

-Dave


Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk