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 2nd, 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:
I am requesting permission to merge this commit to master in multiprecision: https://github.com/boostorg/multiprecision/pull/661/commits/49ef290b0c22b717.... It fixes a warnings emitted by -Wimplicit-fallthrough. The only CI failure is an s390x machine failed in it's init steps. Matt
On Sun, Mar 16, 2025 at 7:57 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:
I'd like to ask for permission to merge https://github.com/boostorg/python/pull/475/files to master in boost.python. The change is required to support a GIL-free build of Python 3.13. Thanks, -- ...ich hab' noch einen Koffer in Berlin...
On 3/17/25 02:57, Marshall Clow 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 April 2nd, master closes for all changes.
As always, the calendar is at https://www.boost.org/development/
I would like to merge this commit to Boost.Log master: https://github.com/boostorg/log/commit/724e888b5a558f8dc3db64b4397ce23f83baa... This fixes text_file_backend behavior wrt. initial file counter selection when appending to the last written file is enabled and active file name pattern does not have a counter placeholder but target file name pattern does.
participants (4)
-
Andrey Semashev -
Marshall Clow -
Matt Borland -
Stefan Seefeld