[release] Boost 1.62 closed for major changes.
Reminder Boost 1.62, i.e. the master branches, are now closed for major changes. The only changes that should be going in at this time should be bug fixes for serious problems. Any documentation changes are fine to go in. And remember... Boost 1.62 will close for all changes a week from today. -- -- Rene Rivera -- Grafik - Don't Assume Anything -- Robot Dreams - http://robot-dreams.net -- rrivera/acm.org (msn) - grafikrobot/aim,yahoo,skype,efnet,gmail
Le 18/08/16 à 04:54, Rene Rivera a écrit :
Reminder Boost 1.62, i.e. the master branches, are now closed for major changes. The only changes that should be going in at this time should be bug fixes for serious problems. Any documentation changes are fine to go in.
And remember... Boost 1.62 will close for all changes a week from today.
Hi Rene, Would you please indicate the rev of master concerned by this? I pushed some changes yesterday night and want to be sure they go in. Thanks, Raffi
On Thu, Aug 18, 2016 at 7:01 AM, Raffi Enficiaud < raffi.enficiaud@mines-paris.org> wrote:
Le 18/08/16 à 04:54, Rene Rivera a écrit :
Reminder Boost 1.62, i.e. the master branches, are now closed for major changes. The only changes that should be going in at this time should be bug fixes for serious problems. Any documentation changes are fine to go in.
And remember... Boost 1.62 will close for all changes a week from today.
Hi Rene,
Would you please indicate the rev of master concerned by this? I pushed some changes yesterday night and want to be sure they go in.
There is no rev of master. We aren't stopping the master updating until next week. -- -- Rene Rivera -- Grafik - Don't Assume Anything -- Robot Dreams - http://robot-dreams.net -- rrivera/acm.org (msn) - grafikrobot/aim,yahoo,skype,efnet,gmail
Le 18/08/16 à 14:24, Rene Rivera a écrit :
On Thu, Aug 18, 2016 at 7:01 AM, Raffi Enficiaud < raffi.enficiaud@mines-paris.org> wrote:
Le 18/08/16 à 04:54, Rene Rivera a écrit :
Reminder Boost 1.62, i.e. the master branches, are now closed for major changes. The only changes that should be going in at this time should be bug fixes for serious problems. Any documentation changes are fine to go in.
And remember... Boost 1.62 will close for all changes a week from today.
Hi Rene,
Would you please indicate the rev of master concerned by this? I pushed some changes yesterday night and want to be sure they go in.
There is no rev of master. We aren't stopping the master updating until next week.
Ok :) But there will be one next week, right?
On Thu, Aug 18, 2016 at 7:36 AM, Raffi Enficiaud < raffi.enficiaud@mines-paris.org> wrote:
Le 18/08/16 à 14:24, Rene Rivera a écrit :
On Thu, Aug 18, 2016 at 7:01 AM, Raffi Enficiaud < raffi.enficiaud@mines-paris.org> wrote:
Le 18/08/16 à 04:54, Rene Rivera a écrit :
Reminder Boost 1.62, i.e. the master branches, are now closed for major
changes. The only changes that should be going in at this time should be bug fixes for serious problems. Any documentation changes are fine to go in.
And remember... Boost 1.62 will close for all changes a week from today.
Hi Rene,
Would you please indicate the rev of master concerned by this? I pushed some changes yesterday night and want to be sure they go in.
There is no rev of master. We aren't stopping the master updating until next week.
Ok :) But there will be one next week, right?
Yes, there will be. At some point between next Wednesday and the following Saturday we'll decide on that. And then make a beta based on that rev. Which means now is a good time to get release notes in. -- -- Rene Rivera -- Grafik - Don't Assume Anything -- Robot Dreams - http://robot-dreams.net -- rrivera/acm.org (msn) - grafikrobot/aim,yahoo,skype,efnet,gmail
On 08/18/16 05:54, Rene Rivera wrote:
Reminder Boost 1.62, i.e. the master branches, are now closed for major changes. The only changes that should be going in at this time should be bug fixes for serious problems. Any documentation changes are fine to go in.
And remember... Boost 1.62 will close for all changes a week from today.
Is it too late to synchronize master with develop for circular_buffer? I've created this PR: https://github.com/boostorg/circular_buffer/pull/10 I'm particularly interested in merging my PR#9 [1], which has been in develop for some time. The PR made circular_buffer thread-safe by default in debug mode. [1] https://github.com/boostorg/circular_buffer/pull/9
On Thu, Aug 18, 2016 at 3:19 PM, Andrey Semashev
On 08/18/16 05:54, Rene Rivera wrote:
Reminder Boost 1.62, i.e. the master branches, are now closed for major changes. The only changes that should be going in at this time should be bug fixes for serious problems. Any documentation changes are fine to go in.
And remember... Boost 1.62 will close for all changes a week from today.
Is it too late to synchronize master with develop for circular_buffer? I've created this PR:
https://github.com/boostorg/circular_buffer/pull/10
I'm particularly interested in merging my PR#9 [1], which has been in develop for some time. The PR made circular_buffer thread-safe by default in debug mode.
Looks like a bug fix to me.. So go ahead. And thanks for asking. PS. Wish others asked so nicely.. As I've seen other master changes today which fall considerably on not bug fix but new feature land instead. Makes me want to consider doing a lock down even at this early stage. -- -- Rene Rivera -- Grafik - Don't Assume Anything -- Robot Dreams - http://robot-dreams.net -- rrivera/acm.org (msn) - grafikrobot/aim,yahoo,skype,efnet,gmail
On 08/18/16 23:36, Rene Rivera wrote:
On Thu, Aug 18, 2016 at 3:19 PM, Andrey Semashev
wrote: On 08/18/16 05:54, Rene Rivera wrote:
Reminder Boost 1.62, i.e. the master branches, are now closed for major changes. The only changes that should be going in at this time should be bug fixes for serious problems. Any documentation changes are fine to go in.
And remember... Boost 1.62 will close for all changes a week from today.
Is it too late to synchronize master with develop for circular_buffer? I've created this PR:
https://github.com/boostorg/circular_buffer/pull/10
I'm particularly interested in merging my PR#9 [1], which has been in develop for some time. The PR made circular_buffer thread-safe by default in debug mode.
Looks like a bug fix to me.. So go ahead. And thanks for asking.
Thanks. To be clear, I don't have permissions to merge it, so I'd appreciate if someone did it.
PS. Wish others asked so nicely.. As I've seen other master changes today which fall considerably on not bug fix but new feature land instead. Makes me want to consider doing a lock down even at this early stage.
I've just merged a docs fix in Boost.Log. I hope I didn't create any problems.
On Wed, Aug 17, 2016 at 9:54 PM, Rene Rivera
Reminder Boost 1.62, i.e. the master branches, are now closed for major changes. The only changes that should be going in at this time should be bug fixes for serious problems. Any documentation changes are fine to go in.
And remember... Boost 1.62 will close for all changes a week from today.
Looking at the calendar, it appears that the Beta will drop while I am out of the country, without access to a computer. So unless someone else wants to take a crack at it (I can provide scripts/instructions/a remote desktop environment), the windows build of the beta will be about a week after the source beta. I doubt that matters to too many, just wanted to mention it to the community. Tom
participants (4)
-
Andrey Semashev
-
Raffi Enficiaud
-
Rene Rivera
-
Tom Kent