|
Boost : |
Subject: Re: [boost] 1.56 release
From: John Maddock (boost.regex_at_[hidden])
Date: 2014-03-23 12:39:25
>>> 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
>>>
>>
>> Are we going to do this? Since we haven't got the new branching structure
>> in place, I could stop automatically updating the master branch of the
>> super project on Monday, or perhaps on April 7th.
>
> For preference, I would like to see a clear announcement of what we're
> doing a good week or two before the process starts.
So.... do we have a release schedule yet? There is still nothing listed
on the calendar and IMO something needs to be formally announced in
advance rather than just "hey, lets do it now!" ;-)
Just my 2c... John.
PS would it pay to do a dummy release process *before* starting on the
actual release to make sure all the scripts etc still work? Or maybe
someone has done this already?
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk