Subject: Re: [boost] 1.56 release
From: Tom Kent (lists_at_[hidden])
Date: 2014-03-14 08:01:51
On Thu, Mar 13, 2014 at 1:49 PM, Andrey Semashev
> On Thursday 13 March 2014 11:44:22 Marshall Clow wrote:
>> On Mar 12, 2014, at 1:59 PM, Barend Gehrels <barend_at_[hidden]> wrote:
>> > Hi,
>> > The last message about the release schedule was (if I see it correctly) at
>> > January 15, and the calendar is empty.
>> > Is there more news about the release planning? I'm especially interested
>> > in the planning for the 1.56 release.
>> This is what I'm thinking about:
>> Mar 24 master closed for breaking changes.
>> April 7 master closed, except by permission
>> April 10 build beta 1 RC
>> April 14 release Beta 1, reopen master
>> April 28 master closed, except by permission
>> May 1st build RC
>> May 5th release 1.56.0
> Do you mean the master branch of the superproject?
Presumably including the pointers to each submodule, so the code in
them will not change, even if submodules add changes to master during
Also, would it be worth doing a pre-beta dry-run, to make sure the
build process still works?
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk