Subject: Re: [boost] Let's not forget the release
From: Beman Dawes (bdawes_at_[hidden])
Date: 2014-06-08 11:36:46
On Sun, Jun 8, 2014 at 9:09 AM, James Sharpe <mail_at_[hidden]> wrote:
> On 8 Jun 2014 13:29, "John Maddock" <boost.regex_at_[hidden]> wrote:
> >> We don't have a viable release process in place yet, so we are going to
> >> have to make at least minimal changes.
> >> Straw man proposal:
> >> * On the 16th, (i.e. little more than a week from now) we turn off
> >> automatic sub-module master updates.
> >> * From that point until the release ships, a new library master release
> >> (with bug fixes only!) may be added manually to the Boost release by the
> >> release managers at their discretion. They have to be asked explicitly.
> >> * When the release ships, auto sub-module updates are turned back on.
> > That sounds sensible to me, John.
> Why do you need to stop the submodule updates for master? Surely the
> correct thing to do is create a branch that targets the release.
Interesting question. Unfortunately, we want to keep regression testing on
what will become the release, and don't have an automatic way to switch the
current master testers to a different branch.
Or do we? Rene?
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk