Release branch will be closing Monday night.
We will be “closing” the release branch late Monday night (Pacific Daylight time) in preparation for building a 1.56.0 release candidate on Tuesday morning. [ Actually, we’re just going to stop the automatic merging to the super-project, but … ] Please refrain from committing to the “master” branch of your libraries after 11:59 Monday night. (unless you have specific permission from the release managers) Thank you. — Marshall
Marshall Clow
We will be “closing” the release branch late Monday night (Pacific Daylight time) in preparation for building a 1.56.0 release candidate on Tuesday morning.
[ Actually, we’re just going to stop the automatic merging to the super-project, but … ]
Hi, seems like automerging is indeed already stopped. I request that the following commit to flyweight master: https://github.com/boostorg/flyweight/commit/ eaa5f56b9b16b894541b93ad50718f5bdf3cd6b2 be merged into supermaster. It is a change in testing code, not in the lib itself, and has already cycled through 90% of the test runners in develop. Thank you, Joaquín M López Muñoz Telefónica
Joaquin M Lopez Munoz
Marshall Clow
writes: We will be “closing” the release branch late Monday night (Pacific Daylight time) in preparation for building a 1.56.0 release candidate on Tuesday morning.
[ Actually, we’re just going to stop the automatic merging to the super-project, but … ]
Hi, seems like automerging is indeed already stopped. I request that the following commit to flyweight master [...] be merged into supermaster.
Never mind, I see commitbot is stil in operation and the commit has been merged. Thank you, Joaquín M López Muñoz Telefónica
On 26/07/2014 17:31, Marshall Clow wrote:
We will be “closing” the release branch late Monday night (Pacific Daylight time) in preparation for building a 1.56.0 release candidate on Tuesday morning.
Any chance someone could pull https://github.com/boostorg/smart_ptr/pull/8 before the release freeze? I tried to keep the change trivial to make it "easier" to make the release. See related discussion at http://lists.boost.org/boost-users/2014/07/82537.php.
On 07/27/2014 04:08 PM, Gavin Lambert wrote:
On 26/07/2014 17:31, Marshall Clow wrote:
We will be “closing” the release branch late Monday night (Pacific Daylight time) in preparation for building a 1.56.0 release candidate on Tuesday morning.
Any chance someone could pull https://github.com/boostorg/smart_ptr/pull/8 before the release freeze?
I tried to keep the change trivial to make it "easier" to make the release. See related discussion at http://lists.boost.org/boost-users/2014/07/82537.php.
I'm extremely reluctant to accept any code changes at the 11th hour like this, especially ones that don't fix very serious regressions. I'm willing to be overruled if another release manager feels this rises to the level. \e
On Jul 28, 2014, at 11:26 AM, Eric Niebler
On 07/27/2014 04:08 PM, Gavin Lambert wrote:
On 26/07/2014 17:31, Marshall Clow wrote:
We will be “closing” the release branch late Monday night (Pacific Daylight time) in preparation for building a 1.56.0 release candidate on Tuesday morning.
Any chance someone could pull https://github.com/boostorg/smart_ptr/pull/8 before the release freeze?
I tried to keep the change trivial to make it "easier" to make the release. See related discussion at http://lists.boost.org/boost-users/2014/07/82537.php.
I'm extremely reluctant to accept any code changes at the 11th hour like this, especially ones that don't fix very serious regressions. I'm willing to be overruled if another release manager feels this rises to the level.
We don’t pull into boostorg::master. We merge from the sub-projects. Has this been integrated into smart_ptr? I don’t see it there (either on “develop” or “master”) Are there tests for this change? — Marshall
participants (4)
-
Eric Niebler -
Gavin Lambert -
Joaquin M Lopez Munoz -
Marshall Clow