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 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.

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 request these changes be merged to multiprecision: https://github.com/boostorg/multiprecision/pull/664/files. The issue and patches came in yesterday since Clang 20 now emits -Wdeprecated-literal-operator by default. Thanks. Matt

пн, 17 мар. 2025 г. в 02:57, Marshall Clow via Boost <boost@lists.boost.org>:

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'd like to ask for permission to merge https://github.com/boostorg/type_index/commit/3f72edd06511ccb9ae70942c08ae7e... It fixes an UB that was introduced in Boost.TypeIndex 1.84 and now prevents the library from building on clang-20. -- Best regards, Antony Polukhin

пн, 17 мар. 2025 г. в 02:57, Marshall Clow via Boost <boost@lists.boost.org>:

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.

A user has raised this issue with Context: https://github.com/boostorg/context/issues/297. It is impossible to select the underlying implementation from the command line. The issue affects both the previous release and the one currently being prepared. The fix is already in Context's develop, but never got to master.

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 the following commits to Boost.Iterator master: https://github.com/boostorg/iterator/commit/1a7996ebd07aa15391d77cae6a787f91... Fixes a compilation error in filter_iterator conversion constructor that was introduced in this release. The problem was just reported here: https://github.com/boostorg/iterator/issues/90 https://github.com/boostorg/iterator/commit/c2b846c57dd0bce0f7ab2c91b883e3b9... A test for the above fix.