[release] 1.92.0 post-beta merges: master branch is open
The master branch is is now open for post-beta merges, but only as described in the Post-Beta Merge Policy. See <https://github.com/boostorg/wiki/wiki/Releases%3A-Beta-Merge-Policy>: Summary: Master open for documentation updates. Other changes by permission of a release manager. Boost Calendar with the release schedule: https://www.boost.org/calendar/ Thanks, -- The Boost Release Team
Can I merge the latest B2 version 5.5.2? Changes in it from the current 5.5.1 are https://github.com/bfgroup/b2/releases/tag/5.5.2 On Tue, Jul 14, 2026 at 9:13 AM Ion Gaztañaga via Boost < boost@lists.boost.org> wrote:
The master branch is is now open for post-beta merges, but only as described in the Post-Beta Merge Policy. See <https://github.com/boostorg/wiki/wiki/Releases%3A-Beta-Merge-Policy>:
Summary: Master open for documentation updates. Other changes by permission of a release manager.
Boost Calendar with the release schedule: https://www.boost.org/calendar/
Thanks,
-- The Boost Release Team _______________________________________________ Boost mailing list -- boost@lists.boost.org To unsubscribe send an email to boost-leave@lists.boost.org https://lists.boost.org/mailman3/lists/boost.lists.boost.org/ Archived at: https://lists.boost.org/archives/list/boost@lists.boost.org/message/2ONNF4GI...
-- -- René Ferdinand Rivera Morell -- Don't Assume Anything -- No Supongas Nada -- Robot Dreams - http://robot-dreams.net
Am 14.07.26 um 16:18 schrieb René Ferdinand Rivera Morell via Boost:
Can I merge the latest B2 version 5.5.2? Changes in it from the current 5.5.1 are https://github.com/bfgroup/b2/releases/tag/5.5.2 This includes a regression which makes it harder to use compiler wrappers with the clang-linux toolset. I'd suggest including a fix for that before merging.
El 14/07/2026 a las 16:18, René Ferdinand Rivera Morell via Boost escribió:
Can I merge the latest B2 version 5.5.2? Changes in it from the current 5.5.1 are https://github.com/bfgroup/b2/releases/tag/5.5.2
Go ahead as this fixes a regression. Ion
El 14/07/2026 a las 17:19, Ion Gaztañaga via Boost escribió:
El 14/07/2026 a las 16:18, René Ferdinand Rivera Morell via Boost escribió:
Can I merge the latest B2 version 5.5.2? Changes in it from the current 5.5.1 are https://github.com/bfgroup/b2/releases/tag/5.5.2
Go ahead as this fixes a regression.
Ion
Sorry, I misunderstood the regression issue, but 5.5.2 fixes other issues. Rene, are you going to fix the regression and create 5.5.3 before merging? Best, Ion
вт, 14 июл. 2026 г. в 17:13, Ion Gaztañaga via Boost <boost@lists.boost.org>:
The master branch is is now open for post-beta merges, but only as described in the Post-Beta Merge Policy. See <https://github.com/boostorg/wiki/wiki/Releases%3A-Beta-Merge-Policy>:
Summary: Master open for documentation updates. Other changes by permission of a release manager.
Requesting permission to merge https://github.com/boostorg/stacktrace/commit/4f8cabb87fb35044d5df44ae44cbf5... It's for quite some time on develop, no problems noted -- Best regards, Antony Polukhin
El 20/07/2026 a las 21:18, Antony Polukhin via Boost escribió:
вт, 14 июл. 2026 г. в 17:13, Ion Gaztañaga via Boost <boost@lists.boost.org>:
The master branch is is now open for post-beta merges, but only as described in the Post-Beta Merge Policy. See <https://github.com/boostorg/wiki/wiki/Releases%3A-Beta-Merge-Policy>:
Summary: Master open for documentation updates. Other changes by permission of a release manager.
Requesting permission to merge https://github.com/boostorg/stacktrace/commit/4f8cabb87fb35044d5df44ae44cbf5... It's for quite some time on develop, no problems noted
Go ahead. Best, Ion
El 14/07/2026 a las 16:12, Ion Gaztañaga via Boost escribió:
The master branch is is now open for post-beta merges, but only as described in the Post-Beta Merge Policy. See <https://github.com/boostorg/wiki/wiki/Releases%3A-Beta-Merge-Policy>:
Summary: Master open for documentation updates. Other changes by permission of a release manager.
Boost Calendar with the release schedule: https://www.boost.org/calendar/
Hi, I'm asking for permission to merge these two Boost.PolyCollection PRs to master: * https://github.com/boostorg/poly_collection/pull/33 * https://github.com/boostorg/poly_collection/pull/34 These fix some errors arising in conjunction with libc++ v21 or higher, which was not tested against until recently. PRs are already in develop and CI is all green. Thank you, Joaquín M López Muñoz
El 21/07/2026 a las 18:27, Joaquin M López Muñoz escribió:
Hi, I'm asking for permission to merge these two Boost.PolyCollection PRs to master:
* https://github.com/boostorg/poly_collection/pull/33 * https://github.com/boostorg/poly_collection/pull/34
These fix some errors arising in conjunction with libc++ v21 or higher, which was not tested against until recently. PRs are already in develop and CI is all green.
Please go ahead, Best, Ion
El 21/07/2026 a las 23:31, Ion Gaztañaga escribió:
El 21/07/2026 a las 18:27, Joaquin M López Muñoz escribió:
Hi, I'm asking for permission to merge these two Boost.PolyCollection PRs to master:
* https://github.com/boostorg/poly_collection/pull/33 * https://github.com/boostorg/poly_collection/pull/34
These fix some errors arising in conjunction with libc++ v21 or higher, which was not tested against until recently. PRs are already in develop and CI is all green.
Please go ahead,
Done, thank you. Joaquín M López Muñoz
On Tue, 14 Jul 2026 at 16:13, Ion Gaztañaga via Boost <boost@lists.boost.org> wrote:
The master branch is is now open for post-beta merges, but only as described in the Post-Beta Merge Policy. See <https://github.com/boostorg/wiki/wiki/Releases%3A-Beta-Merge-Policy>:
Summary: Master open for documentation updates. Other changes by permission of a release manager.
Boost Calendar with the release schedule: https://www.boost.org/calendar/
I'd like to report what I think is a problem with Boost.Asio when building with -fsanitize=thread and older compilers (clang-4, gcc-7): https://github.com/chriskohlhoff/asio/issues/1759. The issue is that tsan-related includes seem to have been added some releases after -fsanitize=thread, but Asio does not take this into account. Caught by Boost.MySQL CIs (https://drone.cpp.al/boostorg/mysql/1206/12/5). It'd be nice having a fix before the release, although I wouldn't consider it blocking. I'll disable tsan for these CIs for now. Best, Ruben.
El 27/07/2026 a las 16:14, Ruben Perez escribió:
On Tue, 14 Jul 2026 at 16:13, Ion Gaztañaga via Boost <boost@lists.boost.org> wrote:
The master branch is is now open for post-beta merges, but only as described in the Post-Beta Merge Policy. See <https://github.com/boostorg/wiki/wiki/Releases%3A-Beta-Merge-Policy>:
Summary: Master open for documentation updates. Other changes by permission of a release manager.
Boost Calendar with the release schedule: https://www.boost.org/calendar/
I'd like to report what I think is a problem with Boost.Asio when building with -fsanitize=thread and older compilers (clang-4, gcc-7): https://github.com/chriskohlhoff/asio/issues/1759. The issue is that tsan-related includes seem to have been added some releases after -fsanitize=thread, but Asio does not take this into account. Caught by Boost.MySQL CIs (https://drone.cpp.al/boostorg/mysql/1206/12/5).
It'd be nice having a fix before the release, although I wouldn't consider it blocking. I'll disable tsan for these CIs for now.
Hi Ruben, It doesn't seem a blocker issue, and probably it won't be fixed soon (there 900+ open issues in Asio), thanks for the report. Best, Ion
Hi, I'm asking for permission to merge this PR to Boost.Graph master> https://github.com/boostorg/graph/pull/544 This PR brings documentation fixes that work on develop to the master branch. Thank you, Arnaud On Mon, Jul 27, 2026 at 10:41 PM Ion Gaztañaga via Boost < boost@lists.boost.org> wrote:
El 27/07/2026 a las 16:14, Ruben Perez escribió:
On Tue, 14 Jul 2026 at 16:13, Ion Gaztañaga via Boost <boost@lists.boost.org> wrote:
The master branch is is now open for post-beta merges, but only as
described in
the Post-Beta Merge Policy. See <https://github.com/boostorg/wiki/wiki/Releases%3A-Beta-Merge-Policy>:
Summary: Master open for documentation updates. Other changes by permission of a release manager.
Boost Calendar with the release schedule: https://www.boost.org/calendar/
I'd like to report what I think is a problem with Boost.Asio when building with -fsanitize=thread and older compilers (clang-4, gcc-7): https://github.com/chriskohlhoff/asio/issues/1759. The issue is that tsan-related includes seem to have been added some releases after -fsanitize=thread, but Asio does not take this into account. Caught by Boost.MySQL CIs (https://drone.cpp.al/boostorg/mysql/1206/12/5).
It'd be nice having a fix before the release, although I wouldn't consider it blocking. I'll disable tsan for these CIs for now.
Hi Ruben,
It doesn't seem a blocker issue, and probably it won't be fixed soon (there 900+ open issues in Asio), thanks for the report.
Best,
Ion _______________________________________________ Boost mailing list -- boost@lists.boost.org To unsubscribe send an email to boost-leave@lists.boost.org https://lists.boost.org/mailman3/lists/boost.lists.boost.org/ Archived at: https://lists.boost.org/archives/list/boost@lists.boost.org/message/EBRR47IT...
El 29/07/2026 a las 12:27, Arnaud Becheler escribió:
Hi, I'm asking for permission to merge this PR to Boost.Graph master>
https://github.com/boostorg/graph/pull/544 <https://github.com/boostorg/graph/ pull/544>
This PR brings documentation fixes that work on develop to the master branch.
Thank you, Arnaud
Go ahead, documentation changes are not critical on this post-beta phase. Best, Ion
On Tue, 14 Jul 2026 at 16:13, Ion Gaztañaga via Boost <boost@lists.boost.org> wrote:
The master branch is is now open for post-beta merges, but only as described in the Post-Beta Merge Policy. See <https://github.com/boostorg/wiki/wiki/Releases%3A-Beta-Merge-Policy>:
Summary: Master open for documentation updates. Other changes by permission of a release manager.
Boost Calendar with the release schedule: https://www.boost.org/calendar/
Hi, I'd like to request permission to merge this commit to Boost.MySQL: https://github.com/boostorg/mysql/commit/466675d89aaac199118c5ff65676fc9a552... It fixes a case of undefined behavior when reading packets from the server that exceed ((std::numeric_limits<std::size_t>::max() >> 1) + 1) in size. The UB case was introduced during this release. I'm concerned that it may be eventually exploitable, so I'd prefer to ship it before the release. Thanks, Ruben.
Thanks,
-- The Boost Release Team _______________________________________________ Boost mailing list -- boost@lists.boost.org To unsubscribe send an email to boost-leave@lists.boost.org https://lists.boost.org/mailman3/lists/boost.lists.boost.org/ Archived at: https://lists.boost.org/archives/list/boost@lists.boost.org/message/2ONNF4GI...
El 29/07/2026 a las 18:27, Ruben Perez escribió:
On Tue, 14 Jul 2026 at 16:13, Ion Gaztañaga via Boost <boost@lists.boost.org> wrote:
The master branch is is now open for post-beta merges, but only as described in the Post-Beta Merge Policy. See <https://github.com/boostorg/wiki/wiki/Releases%3A-Beta-Merge-Policy>:
Summary: Master open for documentation updates. Other changes by permission of a release manager.
Boost Calendar with the release schedule: https://www.boost.org/calendar/
Hi,
I'd like to request permission to merge this commit to Boost.MySQL: https://github.com/boostorg/mysql/commit/466675d89aaac199118c5ff65676fc9a552...
It fixes a case of undefined behavior when reading packets from the server that exceed ((std::numeric_limits<std::size_t>::max() >> 1) + 1) in size. The UB case was introduced during this release. I'm concerned that it may be eventually exploitable, so I'd prefer to ship it before the release.
Thanks, Ruben.
Go ahead, curious to see if returning "(size_t)-1" from a function called "next_power_of_two" won't give you problems in the future ;-) Best, Ion
I'd like to merge these commits to mqtt5: https://github.com/boostorg/mqtt5/commit/31403d6b765daa4afb4dc243f32e4fe7e31... adds a missing guard to prevent multiple client initiations, reported in https://github.com/boostorg/mqtt5/issues/54. https://github.com/boostorg/mqtt5/commit/da37f3975029329cc8b8943eb83bab27964... qualifies calls of internal helper function to avoid ADL ambiguity. https://github.com/boostorg/mqtt5/commit/0e08e614a4c00e35e7bcf7b9d0f9009712f... adds missing bounds checks in the packet decoders. CI is green. Thanks, Bruno Iljazović
El 30/07/2026 a las 17:58, Bruno Iljazović via Boost escribió:
I'd like to merge these commits to mqtt5:
https://github.com/boostorg/mqtt5/commit/31403d6b765daa4afb4dc243f32e4fe7e31... adds a missing guard to prevent multiple client initiations, reported in https://github.com/boostorg/mqtt5/issues/54.
https://github.com/boostorg/mqtt5/commit/da37f3975029329cc8b8943eb83bab27964... qualifies calls of internal helper function to avoid ADL ambiguity.
https://github.com/boostorg/mqtt5/commit/0e08e614a4c00e35e7bcf7b9d0f9009712f... adds missing bounds checks in the packet decoders.
Go ahead and merge. Please review master branch CI to detect if this breaks anything in on that branch. Best, Ion
participants (8)
-
Alexander Grund -
Antony Polukhin -
Arnaud Becheler -
Bruno Iljazović -
Ion Gaztañaga -
Joaquin M López Muñoz -
René Ferdinand Rivera Morell -
Ruben Perez