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
Requesting permission to merge to the master branch of LexicalCast the following commit https://github.com/boostorg/lexical_cast/commit/4b0d10a1f3ec33f7aac28dbf03b1... Best regards, Antony Polukhin On Wed, Mar 11, 2026, 17:12 Marshall Clow via Boost <boost@lists.boost.org> wrote:
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 _______________________________________________ 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/PVY2BNKD...
On Mar 24, 2026, at 10:53 AM, Antony Polukhin <antoshkka@gmail.com> wrote:
Requesting permission to merge to the master branch of LexicalCast the following commit https://github.com/boostorg/lexical_cast/commit/4b0d10a1f3ec33f7aac28dbf03b1...
Go ahead. — Marshall
I'd like to merge the commits from this PR to master: https://github.com/boostorg/msm/pull/201 They fix a bug related to errorneous transition selection as well as warnings about redundant semicolons if -Wpedantic is active. They also fix ODR violations in test code in case multiple tests are linked into a single executable.
On Mar 27, 2026, at 4:15 PM, Christian Granzin via Boost <boost@lists.boost.org> wrote:
I'd like to merge the commits from this PR to master: https://github.com/boostorg/msm/pull/201
They fix a bug related to errorneous transition selection as well as warnings about redundant semicolons if -Wpedantic is active. They also fix ODR violations in test code in case multiple tests are linked into a single executable.
Go ahead. — Marshall
Hi, I ask for permission to merge two patches from develop to master in Boost.Histogram fix: support sparse storage with accumulators (#421) https://github.com/boostorg/histogram/pull/421 Remove dependencies on Boost.StaticAssert. (#419) https://github.com/boostorg/histogram/pull/419 #419 is trivial. #421 fixes a bug which we apparently had for a long time, but which people now discovered because they found a use-case for histograms with sparse storage, something which we supported since the beginning, but we forgot to test the combination of sparse storage and accumulators. Both changes are narrow and pass the tests on Github. On Wed, Mar 11, 2026 at 3:13 PM Marshall Clow via Boost < boost@lists.boost.org> wrote:
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 _______________________________________________ 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/PVY2BNKD...
The master branch is now open for bug fixes, test and documentation changes, but please follow the policy described in:
I am requesting permission to merge the following PR to Decimal: https://github.com/boostorg/decimal/pull/1366/changes. This fixes a bug where a decimal value close to epsilon that is then cast into an integral type results in giant value instead of 0. These changes are on develop already, and this PR ran green against master. Matt
On Apr 7, 2026, at 10:50 AM, Matt Borland <matt@mattborland.com> wrote:
The master branch is now open for bug fixes, test and documentation changes, but please follow the policy described in:
I am requesting permission to merge the following PR to Decimal: https://github.com/boostorg/decimal/pull/1366/changes. This fixes a bug where a decimal value close to epsilon that is then cast into an integral type results in giant value instead of 0. These changes are on develop already, and this PR ran green against master.
Go ahead — Marshall
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 at https://www.boost.org/calendar
Taking advantage of the fact that master closing has been postponed to Apr 15, I'm asking permision to merge the following Boost.Unordered PR: https://github.com/boostorg/unordered/pull/346 This is a simple npm audit fix that solves known vulnerabilities in Node.js modules Brace expansion, Convict, Handlebars.js and Picomatch (used for Antora for doc generation). PR has already been merged to develop without problems. Thank you, Joaquín M López Muñoz
On Apr 9, 2026, at 2:00 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 at https://www.boost.org/calendar
Taking advantage of the fact that master closing has been postponed to Apr 15, I'm asking permision to merge the following Boost.Unordered PR:
https://github.com/boostorg/unordered/pull/346
This is a simple npm audit fix that solves known vulnerabilities in Node.js modules Brace expansion, Convict, Handlebars.js and Picomatch (used for Antora for doc generation). PR has already been merged to develop without problems.
Go ahead. — Marshall
Hi, I would like to merge a fix for MSM addressing non-functional copy and move operations in the backmp11 backend: https://github.com/boostorg/msm/pull/206 Copy operations became non-functional due to a regression introduced in version 1.91, where a newly added member was not copyable. Move operations were also non-functional, as they had not yet been implemented. This PR adds the missing move implementations, restores copy functionality, and introduces regression tests to cover both cases. All tests pass successfully. Christian Granzin Am 11.03.2026 um 15:11 schrieb Marshall Clow via Boost:
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 _______________________________________________ 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/PVY2BNKD...
On Apr 12, 2026, at 10:23 AM, Christian Granzin via Boost <boost@lists.boost.org> wrote:
Hi,
I would like to merge a fix for MSM addressing non-functional copy and move operations in the backmp11 backend: https://github.com/boostorg/msm/pull/206
Copy operations became non-functional due to a regression introduced in version 1.91, where a newly added member was not copyable. Move operations were also non-functional, as they had not yet been implemented.
This PR adds the missing move implementations, restores copy functionality, and introduces regression tests to cover both cases. All tests pass successfully.
Christian — I’m a bit concerned because this is a sizable change. But I think you should go ahead. — Marshall
Christian Granzin
Am 11.03.2026 um 15:11 schrieb Marshall Clow via Boost:
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 _______________________________________________ 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/PVY2BNKD...
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/CN2CHZE2...
On Wed, Mar 11, 2026 at 5:43 PM Marshall Clow via Boost <boost@lists.boost.org> wrote:
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.
I would like to request permission to merge the following commits into Boost.Beast: https://github.com/boostorg/beast/commit/04660c613beb459713eec29e03526763865... A trivial change adding a new HTTP field (fully covered by tests). https://github.com/boostorg/beast/commit/d8361d48fe54f16069f540d9742f2a9871d... Documentation change fixing a table layout. https://github.com/boostorg/beast/commit/077efe520d00839def8b997200adfcd4dd8... Documentation update (Changelog and Release Notes). Thank you, Mohammad Nejati
On Apr 13, 2026, at 2:55 PM, Mohammad Nejati <ashtumashtum@gmail.com> wrote:
On Wed, Mar 11, 2026 at 5:43 PM Marshall Clow via Boost <boost@lists.boost.org> wrote:
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.
I would like to request permission to merge the following commits into Boost.Beast:
https://github.com/boostorg/beast/commit/04660c613beb459713eec29e03526763865... A trivial change adding a new HTTP field (fully covered by tests).
https://github.com/boostorg/beast/commit/d8361d48fe54f16069f540d9742f2a9871d... Documentation change fixing a table layout.
https://github.com/boostorg/beast/commit/077efe520d00839def8b997200adfcd4dd8... Documentation update (Changelog and Release Notes).
The doc changes do not require approval. The code change is fine. Go ahead. — Marshall
participants (8)
-
Alexander Grund -
Antony Polukhin -
Christian Granzin -
Hans Dembinski -
Joaquin M López Muñoz -
Marshall Clow -
Matt Borland -
Mohammad Nejati