[release] The 1.87.0 release will close for major changes WEDNESDAY
Calendar here: https://www.boost.org/development/ Next deadline: The master branch will close for the beta next Wednesday. — The release managers
El 28/10/2024 a las 22:18, Ion Gaztañaga via Boost escribió:
Calendar here: https://www.boost.org/development/
Next deadline: The master branch will close for the beta next Wednesday.
— The release managers
May I take this opportunity to gently remind authors to update the release notes doc at: https://github.com/boostorg/website/blob/master/feed/history/boost_1_87_0.qb... Currently, only 8 libraries are listed there. Thank you! Joaquin M Lopez Munoz
On 10/29/24 00:18, Ion Gaztañaga via Boost wrote:
Calendar here: https://www.boost.org/development/
Next deadline: The master branch will close for the beta next Wednesday.
I would like to merge this change to Boost.Log master: https://github.com/boostorg/log/commit/1be88666c525a6ad8efa865c2d56818b9fc5c... This should fix compilation errors caused by recent removal of deprecated APIs in Boost.ASIO.
On Nov 5, 2024, at 8:43 AM, Andrey Semashev via Boost <boost@lists.boost.org> wrote:
On 10/29/24 00:18, Ion Gaztañaga via Boost wrote:
Calendar here: https://www.boost.org/development/
Next deadline: The master branch will close for the beta next Wednesday.
I would like to merge this change to Boost.Log master:
https://github.com/boostorg/log/commit/1be88666c525a6ad8efa865c2d56818b9fc5c...
This should fix compilation errors caused by recent removal of deprecated APIs in Boost.ASIO.
I’d like to point out that permission is not needed to merge yet. That happens after the beta is released. (So, next week) At this point, we rely on the good judgment of the library maintainers to decide what is appropriate. As we approach the Beta release, the guidance is: Release closed for major code changes. Still open for serious problem fixes and docs changes without release manager review. Andrey, if you want an opinion on to whether this is an appropriate change right before the beta release, I’ll be happy to take a look. But you don’t need release manager approval to merge that now. — Marshall
On 11/5/24 20:03, Marshall Clow wrote:
On Nov 5, 2024, at 8:43 AM, Andrey Semashev via Boost <boost@lists.boost.org> wrote:
On 10/29/24 00:18, Ion Gaztañaga via Boost wrote:
Calendar here: https://www.boost.org/development/
Next deadline: The master branch will close for the beta next Wednesday.
I would like to merge this change to Boost.Log master:
https://github.com/boostorg/log/commit/1be88666c525a6ad8efa865c2d56818b9fc5c...
This should fix compilation errors caused by recent removal of deprecated APIs in Boost.ASIO.
I’d like to point out that permission is not needed to merge yet. That happens after the beta is released. (So, next week)
At this point, we rely on the good judgment of the library maintainers to decide what is appropriate. As we approach the Beta release, the guidance is:
Release closed for major code changes. Still open for serious problem fixes and docs changes without release manager review.
Andrey, if you want an opinion on to whether this is an appropriate change right before the beta release, I’ll be happy to take a look. But you don’t need release manager approval to merge that now.
Thanks, I've merged it. I wasn't sure if master was closed or not as the previous deadline said "closed for major code changes", and that typically means "ask the release managers for code changes".
participants (4)
-
Andrey Semashev -
Ion Gaztañaga -
Joaquin M López Muñoz -
Marshall Clow