Master branch is now open for bug fixes
The master branch is now open for bug fixes and documentation changes. Other changes by release manager permission, as described in https://github.com/boostorg/wiki/wiki/Releases%3A-Beta-Merge-Policy Release manager permission is not needed for test changes or documentation changes. The next deadline: On August 7th, master closes for all changes. As always, the calendar is at https://www.boost.org/development/ — Marshall
On Friday, July 26th, 2024 at 2:19 PM, Marshall Clow via Boost <boost@lists.boost.org> wrote:
The master branch is now open for bug fixes and documentation changes.
Other changes by release manager permission, as described in https://github.com/boostorg/wiki/wiki/Releases%3A-Beta-Merge-Policy
Release manager permission is not needed for test changes or documentation changes.
The next deadline: On August 7th, master closes for all changes.
As always, the calendar is at https://www.boost.org/development/
— Marshall
I request permission to merge the following bug fix to master: https://github.com/boostorg/multiprecision/pull/634/commits/317627c43a7517b4.... Last week on the ML we got a report from an OpenSUSE maintainer (CCd) that they were having a packaging issue due to quadmath detection in multiprecision causing build failures with GCC 14. Matt
On 7/26/24 21:19, Marshall Clow via Boost wrote:
The master branch is now open for bug fixes and documentation changes.
Other changes by release manager permission, as described in https://github.com/boostorg/wiki/wiki/Releases%3A-Beta-Merge-Policy
Release manager permission is not needed for test changes or documentation changes.
The next deadline: On August 7th, master closes for all changes.
As always, the calendar is at https://www.boost.org/development/
I would like to merge Boost.Core to master: https://github.com/boostorg/core/compare/master...develop The changes include a workaround for an MSVC bug that affects empty_value, when it is used with a nested class. See more details here: https://github.com/boostorg/core/pull/175 There are also CI and docs changes.
On Jul 26, 2024, at 1:45 PM, Andrey Semashev via Boost <boost@lists.boost.org> wrote:
On 7/26/24 21:19, Marshall Clow via Boost wrote:
The master branch is now open for bug fixes and documentation changes.
Other changes by release manager permission, as described in https://github.com/boostorg/wiki/wiki/Releases%3A-Beta-Merge-Policy
Release manager permission is not needed for test changes or documentation changes.
The next deadline: On August 7th, master closes for all changes.
As always, the calendar is at https://www.boost.org/development/
I would like to merge Boost.Core to master:
https://github.com/boostorg/core/compare/master...develop
The changes include a workaround for an MSVC bug that affects empty_value, when it is used with a nested class. See more details here:
https://github.com/boostorg/core/pull/175
There are also CI and docs changes.
All the changes look harmless except the `empty_value_base` stuff. If you are happy with the test results, go ahead and merge. — Marshall
пт, 26 июл. 2024 г. в 21:20, Marshall Clow via Boost <boost@lists.boost.org>:
The master branch is now open for bug fixes and documentation changes.
Other changes by release manager permission, as described in https://github.com/boostorg/wiki/wiki/Releases%3A-Beta-Merge-Policy
I would like to merge 324a7eb1478083f1c4c29ff460d4ac35d1878726 into master. I got complaints that my deprecation warnings require too generic macro to be silenced. CI passes: https://drone.cpp.al/boostorg/json/1641.
пн, 29 июл. 2024 г. в 20:18, Дмитрий Архипов <grisumbras@gmail.com>:
I would like to merge 324a7eb1478083f1c4c29ff460d4ac35d1878726 into master. I got complaints that my deprecation warnings require too generic macro to be silenced. CI passes: https://drone.cpp.al/boostorg/json/1641.
I forgot to provide a link to the commit: https://github.com/boostorg/json/pull/1031/commits/324a7eb1478083f1c4c29ff46....
On Jul 29, 2024, at 6:32 AM, Дмитрий Архипов via Boost <boost@lists.boost.org> wrote:
пн, 29 июл. 2024 г. в 20:18, Дмитрий Архипов <grisumbras@gmail.com>:
I would like to merge 324a7eb1478083f1c4c29ff460d4ac35d1878726 into master. I got complaints that my deprecation warnings require too generic macro to be silenced. CI passes: https://drone.cpp.al/boostorg/json/1641.
I forgot to provide a link to the commit: https://github.com/boostorg/json/pull/1031/commits/324a7eb1478083f1c4c29ff46....
Go ahead. Do you still have many users using gcc4? — Marshall
пн, 29 июл. 2024 г. в 23:50, Marshall Clow <mclow.lists@gmail.com>:
Do you still have many users using gcc4?
To be honest, I have no idea. I'm deprecating GCC 4, because I plan to use Charconv, and it requires GCC 5+. And I'm doing it now, because CentOS 7 (which used GCC 4.8) just went EOL .
On Tue, Jul 30, 2024, at 5:23 PM, Дмитрий Архипов via Boost wrote:
пн, 29 июл. 2024 г. в 23:50, Marshall Clow <mclow.lists@gmail.com>:
Do you still have many users using gcc4?
To be honest, I have no idea. I'm deprecating GCC 4, because I plan to use Charconv, and it requires GCC 5+. And I'm doing it now, because CentOS 7 (which used GCC 4.8) just went EOL .
I know some people are stuck in 2015. Just the other day: https://stackoverflow.com/a/78790362/85371 ; I don't see that as an argument to not move on though; I think the policies that cause these conservative practices are usually misguided. Just my $0.02
On Sat, Jul 27, 2024 at 2:20 AM Marshall Clow via Boost <boost@lists.boost.org> wrote:
The master branch is now open for bug fixes and documentation changes.
I'd like to merge https://github.com/boostorg/process/commit/9561ebad1c1170ed7a489fc1ced8425f3... into master.
Other changes by release manager permission, as described in https://github.com/boostorg/wiki/wiki/Releases%3A-Beta-Merge-Policy
Release manager permission is not needed for test changes or documentation changes.
The next deadline: On August 7th, master closes for all changes.
As always, the calendar is at https://www.boost.org/development/
— Marshall
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
On Jul 30, 2024, at 5:21 PM, Klemens Morgenstern <klemensdavidmorgenstern@gmail.com> wrote:
On Sat, Jul 27, 2024 at 2:20 AM Marshall Clow via Boost <boost@lists.boost.org> wrote:
The master branch is now open for bug fixes and documentation changes.
I'd like to merge https://github.com/boostorg/process/commit/9561ebad1c1170ed7a489fc1ced8425f3... into master.
That was committed to develop 6 minutes ago ;-) When you’re happy with the test results, go ahead. — Marshall
participants (7)
-
Andrey Semashev -
Klemens Morgenstern -
Marshall Clow -
Matt Borland -
Seth -
Vinnie Falco -
Дмитрий Архипов