[release] Master branch is now open for bug fixes
Hi, The master branch is now open for bug fixes, test and documentation changes, but please follow the policy described in: https://github.com/boostorg/wiki/wiki/Releases%3A-Beta-Merge-Policy The next deadline: On April 1st, the master branch closes for all changes. As always, the calendar is at https://www.boost.org/calendar — The release managers
I'd like to merge a fix for a MSVC warning in one of the tests: https://github.com/boostorg/nowide/pull/208
On Mar 12, 2026, at 1:10 AM, Alexander Grund via Boost <boost@lists.boost.org> wrote:
I'd like to merge a fix for a MSVC warning in one of the tests: https://github.com/boostorg/nowide/pull/208
Go ahead. — Marshall
I’m requesting to merge a bugfix[1] into Math for Ellint2 that was reported to us through the MSVC STL. This fix is on develop and has cycled green with the linked PR to master. Matt [1] https://github.com/boostorg/math/pull/1379
El 11/03/2026 a las 15:11, Marshall Clow via Boost escribió:
Hi,
The master branch is now open for bug fixes, test and documentation changes, but please follow the policy described in:
https://github.com/boostorg/wiki/wiki/Releases%3A-Beta-Merge-Policy
The next deadline: On April 1st, the master branch closes for all changes.
As always, the calendar is athttps://www.boost.org/calendar
I request permission to merge these two PRs in Boost.Unordered: * https://github.com/boostorg/unordered/pull/345 : a trivial security patch with some Node.js vulnerabilities in the Antora setup for doc building. * https://github.com/boostorg/unordered/pull/334 : this solves an interoperability problem with Boost.LEAF (https://github.com/boostorg/unordered/issues/331). Technically, the fix breaks backwards compatibility, but it does so in scenarios that seem very unlikely (plus the user-side fix is trivial). Joaquín M López Muñoz
On Mar 13, 2026, at 4:53 AM, Joaquin M López Muñoz via Boost <boost@lists.boost.org> wrote:
El 11/03/2026 a las 15:11, Marshall Clow via Boost escribió:
Hi,
The master branch is now open for bug fixes, test and documentation changes, but please follow the policy described in:
https://github.com/boostorg/wiki/wiki/Releases%3A-Beta-Merge-Policy
The next deadline: On April 1st, the master branch closes for all changes.
As always, the calendar is athttps://www.boost.org/calendar
I request permission to merge these two PRs in Boost.Unordered: * https://github.com/boostorg/unordered/pull/345 : a trivial security patch with some Node.js vulnerabilities in the Antora setup for doc building. * https://github.com/boostorg/unordered/pull/334 : this solves an interoperability problem with Boost.LEAF (https://github.com/boostorg/unordered/issues/331). Technically, the fix breaks backwards compatibility, but it does so in scenarios that seem very unlikely (plus the user-side fix is trivial). Joaquín M López Muñoz
Go ahead. — Marshall
participants (4)
-
Alexander Grund -
Joaquin M López Muñoz -
Marshall Clow -
Matt Borland