Re: [boost] a release manager for Boost 1.56

Subject: Re: [boost] a release manager for Boost 1.56
From: Barend Gehrels (barend_at_[hidden])
Date: 2014-07-21 17:45:09

Marshall Clow wrote On 21-7-2014 23:39:
> On Jul 21, 2014, at 12:15 PM, Barend Gehrels <barend_at_[hidden]> wrote:
>
>> Hi,
>>
>>
>> Marshall Clow wrote On 21-7-2014 16:00:
>>> On Jul 21, 2014, at 12:49 AM, Andrzej Krzemienski <akrzemi1_at_[hidden]> wrote:
>>>
>>>> 2014-07-16 7:02 GMT+02:00 Eric Niebler <eniebler_at_[hidden]>:
>>>>
>>>>> On 7/15/2014 1:41 AM, Andrzej Krzemienski wrote:
>>>>>> Hi,
>>>>>> According to Boost calendar at http://www.boost.org/community/index.html
>>>>> ,
>>>>>> Master is open for bug fixes and doc changes.
>>>>> Hrm, we're still trying to get out a beta. I think that calendar is wrong.
>>>>>
>>>>>> Can I thus merge this pull request:
>>>>>> https://github.com/boostorg/optional/pull/6, which I consider a fix for
>>>>> a
>>>>>> performance bug, but I anticipate other people may have other opinions?
>>>>> If tests have cycled and they look good, please go ahead.
>>>>>
>>>>>
>>>> Thanks,
>>>> However, it looks like although my changes are in Master, they didn't get
>>>> included in Beta 1 release. Is it enough to put my changes in master at
>>>> this stage to get them included in 1.56 release? Or is there a release
>>>> branch?
>>> Yes, it’s enough to put your changes in master.
>>> No, there isn’t a release branch.
>>> “master” is the release branch; it’s supposed to be ready to release all the time.
>> According to the calendar the master branch closes today ("provisional"). Can someone tell us if that is really the case, because we have to merge then (we prepared it)? And, if it does not close today, when it then will be closed? All these dates are called provisional for 2 months now, but I don't have the impression the schedule is following the provisional dates... But they are the only dates published.
> It is not the case.
> We’re about a week or so behind the schedule; and we will announce here when the master branch closes.

Hi Marshall,

Thanks for your quick reply!

Regards, Barend