[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 December 4th, master closes for all changes. As always, the calendar is at https://www.boost.org/development/ — The release managers

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
I am requesting permission to merge the following commit into Multiprecision: https://github.com/boostorg/multiprecision/pull/643/commits/5108a961f3d7f046.... It fixes the definition of float128_type when using the NVIDIA HPC Compiler (formerly PGI). Locally it fixed the reproducer, and the original issue submitter confirmed that the issue was fixed in his workflow as well. Matt

El 18/11/2024 a las 20:53, Matt Borland via Boost escribió:
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
I am requesting permission to merge the following commit into Multiprecision: https://github.com/boostorg/multiprecision/pull/643/commits/5108a961f3d7f046....
It fixes the definition of float128_type when using the NVIDIA HPC Compiler (formerly PGI). Locally it fixed the reproducer, and the original issue submitter confirmed that the issue was fixed in his workflow as well.
Matt
Develop tests look fine. Please go ahead. Best, Ion

On Sun, Nov 17, 2024 at 7:46 AM Ion Gaztañaga 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
I would like to ask permission to merge these fixes into master: https://github.com/boostorg/process/pull/427
The next deadline: On December 4th, master closes for all changes.
As always, the calendar is at https://www.boost.org/development/
— The release managers
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

El 19/11/2024 a las 0:48, Klemens Morgenstern via Boost escribió:
On Sun, Nov 17, 2024 at 7:46 AM Ion Gaztañaga 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
I would like to ask permission to merge these fixes into master: https://github.com/boostorg/process/pull/427
Please go ahead and make sure regression tests in master are ok after the merge. It seems that windows CI in github are timing out in tests (https://github.com/boostorg/process/actions/runs/11903226593/job/33169766851...), I don't know what can be done about it but it adds a bit of noise... Best, Ion

вс, 17 нояб. 2024 г. в 02:46, Ion Gaztañaga via Boost
The master branch is now open for bug fixes, test and documentation changes, but please follow the policy described in:
Requesting permission to merge https://github.com/boostorg/stacktrace/commit/22982db3f6630de16434150d181e0d... to master It fixes cross compilation https://lists.boost.org/Archives/boost/2024/11/258294.php -- Best regards, Antony Polukhin

El 19/11/2024 a las 12:03, Antony Polukhin via Boost escribió:
вс, 17 нояб. 2024 г. в 02:46, Ion Gaztañaga via Boost
: <...> The master branch is now open for bug fixes, test and documentation changes, but please follow the policy described in:
Requesting permission to merge https://github.com/boostorg/stacktrace/commit/22982db3f6630de16434150d181e0d... to master
It fixes cross compilation https://lists.boost.org/Archives/boost/2024/11/258294.php
Please go ahead and make sure regression tests in master are ok after the merge. Best, Ion

On 11/17/24 02:45, Ion Gaztañaga via Boost 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 December 4th, master closes for all changes.
As always, the calendar is at https://www.boost.org/development/
I would like to merge the following change to Boost.Atomic master: https://github.com/boostorg/atomic/commit/5e2e01666860178591d2616a71f88181dd... This fixes initialization of the atomic wait list on reallocation.

On Nov 21, 2024, at 9:37 AM, Andrey Semashev via Boost
On 11/17/24 02:45, Ion Gaztañaga via Boost 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 December 4th, master closes for all changes.
As always, the calendar is at https://www.boost.org/development/
I would like to merge the following change to Boost.Atomic master:
https://github.com/boostorg/atomic/commit/5e2e01666860178591d2616a71f88181dd...
This fixes initialization of the atomic wait list on reallocation.
Go ahead. — Marshall

El 17/11/2024 a las 0:45, Ion Gaztañaga 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 December 4th, master closes for all changes.
As always, the calendar is at https://www.boost.org/development/
Hi, I would like to merge the following change to Boost.Container master, this bug was reported yesterday: https://github.com/boostorg/container/commit/a0848ceaf14c23c1b18f449bef188d1... Develop regression tests are fine. Best, Ion

On Thu, Nov 21, 2024 at 3:31 PM Ion Gaztañaga via Boost < boost@lists.boost.org> wrote:
Hi,
I would like to merge the following change to Boost.Container master, this bug was reported yesterday:
https://github.com/boostorg/container/commit/a0848ceaf14c23c1b18f449bef188d1...
Develop regression tests are fine.
Please go ahead. Thanks Ion. Glen

El 17/11/2024 a las 0:45, Ion Gaztañaga 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 December 4th, master closes for all changes.
As always, the calendar is at https://www.boost.org/development/
— The release managers
Another day, another bug, so I'd like to merge to master the following commit: https://github.com/boostorg/container/commit/3e70ecfa80f94689e5917e18ac861ad... Bug was reported two days ago: https://github.com/boostorg/container/issues/296 - The commit is confirmed to fix the issue - Develop regression tests are ok. Best, Ion

On Nov 25, 2024, at 5:20 AM, Ion Gaztañaga via Boost
El 17/11/2024 a las 0:45, Ion Gaztañaga 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 December 4th, master closes for all changes. As always, the calendar is at https://www.boost.org/development/ — The release managers
Another day, another bug, so I'd like to merge to master the following commit:
https://github.com/boostorg/container/commit/3e70ecfa80f94689e5917e18ac861ad...
Bug was reported two days ago:
https://github.com/boostorg/container/issues/296
- The commit is confirmed to fix the issue - Develop regression tests are ok.
Go ahead. — Marshall

El 18/11/2024 a las 20:53, Matt Borland via Boost escribió:
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
Hi, I would like to merge the following commits to Geometry
commit b3d35b341ae7a76e8cdb3eac2a13b09d612c5419
commit e13d5d6b2fa42290d7b93e4a5cc6d0a9e2329e6e
commit 9c4d7529b1c03d1e611fa1b55358350eb8c26d46
commit 75469596907b42394fa849ccb92a03370f4592f6
commit a14dc9d2c16210914a7233617a50e45a88693f9c
commit d03167598c485b5303baee555e370672b8cbc316
All of them are bug fixes and they are cherry picked from develop. All
tests are passing in CI; see this testing branch
https://github.com/boostorg/geometry/tree/master_needs_approval
Best,
Vissarion.
On Mon, 25 Nov 2024 at 17:01, Marshall Clow via Boost
On Nov 25, 2024, at 5:20 AM, Ion Gaztañaga via Boost
wrote: El 17/11/2024 a las 0:45, Ion Gaztañaga 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 December 4th, master closes for all changes. As always, the calendar is at https://www.boost.org/development/ — The release managers
Another day, another bug, so I'd like to merge to master the following commit:
https://github.com/boostorg/container/commit/3e70ecfa80f94689e5917e18ac861ad...
Bug was reported two days ago:
https://github.com/boostorg/container/issues/296
- The commit is confirmed to fix the issue - Develop regression tests are ok.
Go ahead.
— Marshall
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

El 26/11/2024 a las 10:00, Vissarion Fisikopoulos via Boost escribió:
El 18/11/2024 a las 20:53, Matt Borland via Boost escribió:
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
Hi, I would like to merge the following commits to Geometry
commit b3d35b341ae7a76e8cdb3eac2a13b09d612c5419 commit e13d5d6b2fa42290d7b93e4a5cc6d0a9e2329e6e commit 9c4d7529b1c03d1e611fa1b55358350eb8c26d46 commit 75469596907b42394fa849ccb92a03370f4592f6 commit a14dc9d2c16210914a7233617a50e45a88693f9c commit d03167598c485b5303baee555e370672b8cbc316
All of them are bug fixes and they are cherry picked from develop. All tests are passing in CI; see this testing branch https://github.com/boostorg/geometry/tree/master_needs_approval
Hi, To be honest, those commits are not simple, you should have merged them before the beta release. Now, evaluating these changes and under the policy "stability is a major concern at this point in the release cycle": - Regression tests seem fine - Geometry has no reverse dependencies (no other Boost library depends on geometry) So please merge them and review the regression tests on the master branch. Please revert changes if the tests show errors. Best, Ion

El 17/11/2024 a las 0:45, Ion Gaztañaga 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 December 4th, master closes for all changes.
As always, the calendar is at https://www.boost.org/development/
— The release managers
Another day, another bug: Bug: https://github.com/boostorg/move/issues/57 Fix: https://github.com/boostorg/move/commit/b7a04d320104dff1f0ed335addadbb65e9a0... Develop regression tests OK for the commit: https://github.com/boostorg/move/actions/runs/12057774672/job/33623124544 Best, Ion

I'd like to merge these two commits in Boost.MySQL into master: https://github.com/boostorg/mysql/compare/master...develop/ They contain doc changes and a CI fix. While I think I don't need permission to do this, the doc changes aren't small, so I thought I'd ask first. CIs are fine in develop. Thanks, Ruben.

El 01/12/2024 a las 19:18, Ruben Perez via Boost escribió:
I'd like to merge these two commits in Boost.MySQL into master: https://github.com/boostorg/mysql/compare/master...develop/
They contain doc changes and a CI fix. While I think I don't need permission to do this, the doc changes aren't small, so I thought I'd ask first. CIs are fine in develop.
Hi, You don't need permission for that, but please make sure master documentation still builds fine after the merge. Best, Ion

On 11/17/24 02:45, Ion Gaztañaga via Boost 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 December 4th, master closes for all changes.
As always, the calendar is at https://www.boost.org/development/
I would like to merge the following commits to Boost.Integer master: https://github.com/boostorg/integer/commit/b774aa0d9e18df6d71a27d7511afd0e79... Non-essential, just removes some code duplication. https://github.com/boostorg/integer/commit/2dfe66886d71b9a341433ea8b6ff225cc... Fixes a warning with gcc 15 in C++26 mode.

On 11/17/24 02:45, Ion Gaztañaga via Boost 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 December 4th, master closes for all changes.
As always, the calendar is at https://www.boost.org/development/
boost.cobalt doesn't get installed at the moment, because the call-if : boost-library cobalt ; in /build.jam does not include an install. Rene tells me the current build/Jamfile doesn't work for the install either, so I am at a bit of a loss. I would like this to be fixed, as users will expect stage/lib to contain cobalt after they built it, but since it's a new feature I don't know how to. Also (less important), I would like to see if I can merge these two fixes: https://github.com/boostorg/cobalt/compare/master...develop

On Dec 2, 2024, at 9:32 AM, Andrey Semashev via Boost
On 11/17/24 02:45, Ion Gaztañaga via Boost 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 December 4th, master closes for all changes.
As always, the calendar is at https://www.boost.org/development/
I would like to merge the following commits to Boost.Integer master:
https://github.com/boostorg/integer/commit/b774aa0d9e18df6d71a27d7511afd0e79...
Non-essential, just removes some code duplication.
https://github.com/boostorg/integer/commit/2dfe66886d71b9a341433ea8b6ff225cc...
Fixes a warning with gcc 15 in C++26 mode.
Go ahead. — Marshall

On Sun, Nov 17, 2024 at 7:46 AM Ion Gaztañaga 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 December 4th, master closes for all changes.
As always, the calendar is at https://www.boost.org/development/
— The release managers
I would like to merge this commit into master: https://github.com/boostorg/cobalt/commit/8cea71fd8215fb2cdc11569621eb0f3b2b... It works in the boost CI job and I tested locally that it does build with cxxstd=20 and does not with cxxstd=11. https://github.com/boostorg/boost/actions/runs/12138308690
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

El 04/12/2024 a las 1:25, Klemens Morgenstern via Boost escribió:
On Sun, Nov 17, 2024 at 7:46 AM Ion Gaztañaga 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 December 4th, master closes for all changes.
As always, the calendar is at https://www.boost.org/development/
— The release managers
I would like to merge this commit into master:
https://github.com/boostorg/cobalt/commit/8cea71fd8215fb2cdc11569621eb0f3b2b...
It works in the boost CI job and I tested locally that it does build with cxxstd=20 and does not with cxxstd=11.
Please go ahead and make sure regression tests are fine. We will close master very soon... Best, Ion
participants (9)
-
Andrey Semashev
-
Antony Polukhin
-
Glen Fernandes
-
Ion Gaztañaga
-
Klemens Morgenstern
-
Marshall Clow
-
Matt Borland
-
Ruben Perez
-
Vissarion Fisikopoulos