Subject: Re: [boost] Let's not forget the release
From: Tom Kent (lists_at_[hidden])
Date: 2014-06-09 08:52:52
On Sun, Jun 8, 2014 at 4:39 PM, Rene Rivera <grafikrobot_at_[hidden]> wrote:
> On Sun, Jun 8, 2014 at 10:36 AM, Beman Dawes <bdawes_at_[hidden]> wrote:
> > Interesting question. Unfortunately, we want to keep regression testing
> > what will become the release, and don't have an automatic way to switch
> > 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.
For the future (probably not this release), could we have the regression
testers use a tag like "release-prep", which could point to different
branches depending on what the release team needs to see? Most of the
deveopment cycle, this would point to master, but as release branches are
created, it could be updated in the script (or by some flag on a webpage,
etc) to point to a different branch.
This would mean that master isn't having any tests run on it during this
period, but if we stop the submodule updates, we won't really be doing any
tests on the current master either.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk