[release] 1.70.0 closed for major changes
The master branch is now closed for new libraries and breaking changes, and will be closing for the beta in one week. Also, if you're ready, you can also add your libraries' changes to the release notes at: < https://github.com/boostorg/website/blob/master/feed/history/boost_1_69_0.qb...
After editing the release notes, you should get a form to create a pull request, remember to submit it, otherwise I won't see your change. As always, the calendar for the release cycle is available at: https://www.boost.org/development/ Thanks, -- The Boost Release Team
On Sat, Feb 23, 2019 at 10:20 AM Marshall Clow via Boost
The master branch is now closed for new libraries and breaking changes, and will be closing for the beta in one week.
This is suprising to me, I thought I had until March 6, according to this: https://github.com/boostorg/boost/wiki/Releases%3A-Schedule Beast is not ready, I planned for the 6th... Thanks
On 2019-02-23 1:19 p.m., Marshall Clow via Boost wrote:
The master branch is now closed for new libraries and breaking changes, and will be closing for the beta in one week.
According to https://www.boost.org/development/index.html, it's "closed for new libraries" since the 20th, will be "closed for major changes" on the 27th, and will be "completely closed" on March 9th. Would you please clarify the release schedule (and correct the calendar and wiki, if needed), so we can adjust (if possible) ? Thanks, Stefan -- ...ich hab' noch einen Koffer in Berlin...
On Sat, Feb 23, 2019 at 8:46 AM Stefan Seefeld via Boost < boost@lists.boost.org> wrote:
On 2019-02-23 1:19 p.m., Marshall Clow via Boost wrote:
The master branch is now closed for new libraries and breaking changes, and will be closing for the beta in one week.
According to https://www.boost.org/development/index.html, it's "closed for new libraries" since the 20th, will be "closed for major changes" on the 27th,
and will be "completely closed" on March 9th.
Would you please clarify the release schedule (and correct the calendar and wiki, if needed), so we can adjust (if possible) ?
We are closed for "breaking changes" , not "Major changes" and we will be closing for the beta in TWO weeks. Sorry for the panic. -- Marshall
On 2/23/19 9:19 PM, Marshall Clow via Boost wrote:
The master branch is now closed for new libraries and breaking changes, and will be closing for the beta in one week.
Also, if you're ready, you can also add your libraries' changes to the release notes at:
< https://github.com/boostorg/website/blob/master/feed/history/boost_1_69_0.qb...
That should be: https://github.com/boostorg/website/blob/master/feed/history/boost_1_70_0.qb...
On 2019-02-23 2:41 p.m., Marshall Clow via Boost wrote:
On Sat, Feb 23, 2019 at 8:46 AM Stefan Seefeld via Boost < boost@lists.boost.org> wrote:
On 2019-02-23 1:19 p.m., Marshall Clow via Boost wrote:
The master branch is now closed for new libraries and breaking changes, and will be closing for the beta in one week.
According to https://www.boost.org/development/index.html, it's "closed for new libraries" since the 20th, will be "closed for major changes" on the 27th,
and will be "completely closed" on March 9th.
Would you please clarify the release schedule (and correct the calendar and wiki, if needed), so we can adjust (if possible) ?
We are closed for "breaking changes" , not "Major changes" and we will be closing for the beta in TWO weeks. Sorry for the panic.
Edward Diener has been leading the push to merge the new Boost.Parameter changes to master for 1.70, but I think he's still at a conference right now. Cromwell D. Enage
We are closed for "breaking changes" , not "Major changes" and we will be closing for the beta in TWO weeks. Sorry for the panic. Edward Diener has been leading the push to merge the new Boost.Parameter changes to master for 1.70, but I think he's still at a conference right now.
Good point, the Graph lib is currently stuck until this is merged: https://github.com/boostorg/graph/pull/164 John. --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus
On 23.02.19 19:19, Marshall Clow via Boost wrote:
The master branch is now closed for new libraries and breaking changes, and will be closing for the beta in one week.
Also, if you're ready, you can also add your libraries' changes to the release notes at:
< https://github.com/boostorg/website/blob/master/feed/history/boost_1_69_0.qb...
After editing the release notes, you should get a form to create a pull request, remember to submit it, otherwise I won't see your change.
As always, the calendar for the release cycle is available at: https://www.boost.org/development/
I would like to merge the following hashes to master: 37dfcf211739284e0fcd754f6e15fa70be310677 definition of WINNT if not defined 0ed5a9a71f0f1bf3de883eeb11f2aad292542e5a ability to make boost.test work w. Peter Dimov Cmake definitions in b2 c7066f7f9a32186aeb9d876cc92d0b388e04e341 extension of template test cases to any variadic template type All those are green on my CI, but there are some failures on the regression matrix for a new test - already in master before the deadline https://github.com/boostorg/test/blob/develop/test/writing-test-ts/test-time... - that apparently 37dfcf211739284e0fcd754f6e15fa70be310677 did not solve. Those commits would close the issues for boost.test, the remaining tasks being about documentation. Thanks, Raffi
On Wed, Mar 6, 2019 at 10:31 PM Raffi Enficiaud via Boost < boost@lists.boost.org> wrote:
On 23.02.19 19:19, Marshall Clow via Boost wrote:
The master branch is now closed for new libraries and breaking changes, and will be closing for the beta in one week.
Also, if you're ready, you can also add your libraries' changes to the release notes at:
<
https://github.com/boostorg/website/blob/master/feed/history/boost_1_69_0.qb...
After editing the release notes, you should get a form to create a pull request, remember to submit it, otherwise I won't see your change.
As always, the calendar for the release cycle is available at: https://www.boost.org/development/
I would like to merge the following hashes to master:
37dfcf211739284e0fcd754f6e15fa70be310677 definition of WINNT if not defined 0ed5a9a71f0f1bf3de883eeb11f2aad292542e5a ability to make boost.test work w. Peter Dimov Cmake definitions in b2 c7066f7f9a32186aeb9d876cc92d0b388e04e341 extension of template test cases to any variadic template type
All those are green on my CI, but there are some failures on the regression matrix for a new test - already in master before the deadline
https://github.com/boostorg/test/blob/develop/test/writing-test-ts/test-time... - that apparently 37dfcf211739284e0fcd754f6e15fa70be310677 did not solve.
Those commits would close the issues for boost.test, the remaining tasks being about documentation.
If you can do it this morning (PST), then yes. -- Marshall
On 07.03.19 15:36, Marshall Clow via Boost wrote:
On Wed, Mar 6, 2019 at 10:31 PM Raffi Enficiaud via Boost < boost@lists.boost.org> wrote:
On 23.02.19 19:19, Marshall Clow via Boost wrote:
The master branch is now closed for new libraries and breaking changes, and will be closing for the beta in one week.
Also, if you're ready, you can also add your libraries' changes to the release notes at:
<
https://github.com/boostorg/website/blob/master/feed/history/boost_1_69_0.qb...
After editing the release notes, you should get a form to create a pull request, remember to submit it, otherwise I won't see your change.
As always, the calendar for the release cycle is available at: https://www.boost.org/development/
I would like to merge the following hashes to master:
37dfcf211739284e0fcd754f6e15fa70be310677 definition of WINNT if not defined 0ed5a9a71f0f1bf3de883eeb11f2aad292542e5a ability to make boost.test work w. Peter Dimov Cmake definitions in b2 c7066f7f9a32186aeb9d876cc92d0b388e04e341 extension of template test cases to any variadic template type
All those are green on my CI, but there are some failures on the regression matrix for a new test - already in master before the deadline
https://github.com/boostorg/test/blob/develop/test/writing-test-ts/test-time... - that apparently 37dfcf211739284e0fcd754f6e15fa70be310677 did not solve.
Those commits would close the issues for boost.test, the remaining tasks being about documentation.
If you can do it this morning (PST), then yes. -- Marshall
Just came back from work (CET), and merged. I do not know if this is ok. Thanks in all cases! Raffi
participants (7)
-
Andrey Semashev -
Cromwell Enage -
John Maddock -
Marshall Clow -
Raffi Enficiaud -
Stefan Seefeld -
Vinnie Falco