Re: [boost] Let's not forget the release

Subject: Re: [boost] Let's not forget the release
From: Rene Rivera (grafikrobot_at_[hidden])
Date: 2014-06-08 12:39:46

On Sun, Jun 8, 2014 at 10:36 AM, Beman Dawes <bdawes_at_[hidden]> wrote:

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

It's actually easy for the testers.. As all they have to do is change the
"--tag=master" option to something else. The "hard" one is spinning up more
resources to process the output and post test results. Also of note is that
we likely don't have enough testing resources to run an additional branch.
We would have to have the current master testers switch to something else.
And the master results would then stop updating.

-- 
-- Rene Rivera
-- Grafik - Don't Assume Anything
-- Robot Dreams - http://robot-dreams.net
-- rrivera/acm.org (msn) - grafikrobot/aim,yahoo,skype,efnet,gmail