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 The next deadline: On December 7th, master closes for all changes. As always, the calendar is at https://www.boost.org/development/ <https://www.boost.org/development/> — Marshall
I'd like to ask for permission to merge the boost.python's `devel` branch to `master`. There are a few minor bugfixes accumulated over recent months, all tested and stable, but I unfortunately missed the previous window to merge those into master. Thanks, On Thu, Nov 17, 2022 at 9:23 AM 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
The next deadline: On December 7th, master closes for all changes.
As always, the calendar is at https://www.boost.org/development/ < https://www.boost.org/development/>
— Marshall
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
-- ...ich hab' noch einen Koffer in Berlin...
On Nov 17, 2022, at 6:28 AM, Stefan Seefeld via Boost <boost@lists.boost.org> wrote:
I'd like to ask for permission to merge the boost.python's `devel` branch to `master`. There are a few minor bugfixes accumulated over recent months, all tested and stable, but I unfortunately missed the previous window to merge those into master.
Do they all fit into the categories listed below? (https://github.com/boostorg/wiki/wiki/Releases%3A-Beta-Merge-Policy <https://github.com/boostorg/wiki/wiki/Releases:-Beta-Merge-Policy>) • Showstoppers. Criteria: Bugs or other problems so serious that the release is seriously compromised if not fixed. Procedure: After discussion on the developers list, release managers will specify how the problem is to be attacked, and what effect it will have on schedule. • Code changes and fixes. Procedure: Ask release managers for permission. Libraries with regressions showing in trunk testing should not be merged into the release branch. If it is discovered that this has occurred, then the merge should be reverted. Rationale: While we do want to fix problems, particularly regressions, stability is a major concern at this point in the release cycle. • Documentation fixes and other minor changes not affecting code. Criteria: Changes not requiring regression testing and unlikely to impact other libraries. Procedure: Merges to branches/release are OK, after fix applied to trunk, and do not require a release manager's permission. Important: If applicable, check the daily snapshot to verify the change did not break the documentation build. — Marshall
Thanks,
On Thu, Nov 17, 2022 at 9:23 AM 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
The next deadline: On December 7th, master closes for all changes.
As always, the calendar is at https://www.boost.org/development/ < https://www.boost.org/development/>
— Marshall
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
--
...ich hab' noch einen Koffer in Berlin...
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Marshall Clow 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
I have the following merge candidates: numeric/conversion: https://github.com/boostorg/numeric_conversion/commit/50a1eae942effb0a9b9072... Fixes compilation under the new Clang 16, which rejects out of range enum values in constant expressions. (This affects Boost.Log and probably others.) Issue: https://github.com/boostorg/numeric_conversion/issues/24 tools/boost_install: https://github.com/boostorg/boost_install/commit/56f7c5da02a62c009954bfa0c9c... Allows toolset detection when using find_package(Boost) from CMake to recognize the new LLVM-based Intel compiler. Issue: https://github.com/boostorg/boost_install/issues/60 https://github.com/boostorg/boost_install/commit/534727e8a0583d4fb57d943a6e4... Allows Boost_COMPILER to be set to a list of toolsets, similarly to FindBoost in CMake 3.7 or later. Issue: https://github.com/boostorg/boost_install/issues/63
On Nov 17, 2022, at 8:34 AM, Peter Dimov via Boost <boost@lists.boost.org> wrote:
Marshall Clow 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
I have the following merge candidates:
numeric/conversion:
https://github.com/boostorg/numeric_conversion/commit/50a1eae942effb0a9b9072...
Fixes compilation under the new Clang 16, which rejects out of range enum values in constant expressions. (This affects Boost.Log and probably others.)
As far as I know, clang16 won’t be released until the spring, (current release is 15.0.4), but people are using clang trunk and running into this problem.
Issue: https://github.com/boostorg/numeric_conversion/issues/24
tools/boost_install:
https://github.com/boostorg/boost_install/commit/56f7c5da02a62c009954bfa0c9c...
Allows toolset detection when using find_package(Boost) from CMake to recognize the new LLVM-based Intel compiler.
Issue: https://github.com/boostorg/boost_install/issues/60
https://github.com/boostorg/boost_install/commit/534727e8a0583d4fb57d943a6e4...
Allows Boost_COMPILER to be set to a list of toolsets, similarly to FindBoost in CMake 3.7 or later.
Go ahead. — Marshall
I'd like to ask for permission to merge the following fix in Boost.URL: Commit: https://github.com/boostorg/url/commit/1d87343ea756b669baf836914d4b1d78cdba5... Issue: https://github.com/boostorg/url/issues/627 These are auxiliary classes that had virtual functions but not virtual destructors, which were triggering C4265 in MSVC. Em qui., 17 de nov. de 2022 às 13:47, Marshall Clow via Boost < boost@lists.boost.org> escreveu:
On Nov 17, 2022, at 8:34 AM, Peter Dimov via Boost <boost@lists.boost.org> wrote:
Marshall Clow 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
I have the following merge candidates:
numeric/conversion:
https://github.com/boostorg/numeric_conversion/commit/50a1eae942effb0a9b9072...
Fixes compilation under the new Clang 16, which rejects out of range
enum
values in constant expressions. (This affects Boost.Log and probably others.)
As far as I know, clang16 won’t be released until the spring, (current release is 15.0.4), but people are using clang trunk and running into this problem.
Issue: https://github.com/boostorg/numeric_conversion/issues/24
tools/boost_install:
https://github.com/boostorg/boost_install/commit/56f7c5da02a62c009954bfa0c9c...
Allows toolset detection when using find_package(Boost) from CMake to recognize the new LLVM-based Intel compiler.
https://github.com/boostorg/boost_install/commit/534727e8a0583d4fb57d943a6e4...
Allows Boost_COMPILER to be set to a list of toolsets, similarly to
FindBoost
in CMake 3.7 or later.
Go ahead.
— Marshall
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
-- Alan Freitas https://alandefreitas.github.io/alandefreitas/ <https://github.com/alandefreitas>
On Nov 17, 2022, at 9:57 PM, Alan de Freitas via Boost <boost@lists.boost.org> wrote:
I'd like to ask for permission to merge the following fix in Boost.URL:
Commit: https://github.com/boostorg/url/commit/1d87343ea756b669baf836914d4b1d78cdba5... Issue: https://github.com/boostorg/url/issues/627
These are auxiliary classes that had virtual functions but not virtual destructors, which were triggering C4265 in MSVC.
Go ahead. — Marshall
On 11/17/22 17:23, 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
The next deadline: On December 7th, master closes for all changes.
As always, the calendar is at https://www.boost.org/development/ <https://www.boost.org/development/>
I'd like to ask for permission to merge Boost.Iterator to master: https://github.com/boostorg/iterator/commit/7c9b4296a189f71b28de3aad025b08da... Fixes compilation errors when result of post-increment of an iterator is dereferenced and used to access a member of the value. This was discovered in Boost.Filesystem tests.
On Fri, Nov 18, 2022 at 3:42 AM Andrey Semashev wrote:
I'd like to ask for permission to merge Boost.Iterator to master:
https://github.com/boostorg/iterator/commit/7c9b4296a189f71b28de3aad025b08da...
Fixes compilation errors when result of post-increment of an iterator is dereferenced and used to access a member of the value. This was discovered in Boost.Filesystem tests.
Go ahead. Glen
On 17/11/2022 14:23, 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
The next deadline: On December 7th, master closes for all changes.
As always, the calendar is at https://www.boost.org/development/ <https://www.boost.org/development/>
Looks like I forgot to merge develop into master branch before the cutoff again. Sigh. It's all bug fixes since last Boost release, except for a header path rename in Experimental Outcome which might break some code using Experimental Outcome. Here's the changelog: Enhancements: Update to latest status-code in Experimental.Outcome, which relocates its header files and may cause some end user inclusions to need path changes. Bug fixes: Latest status-code fixes a number of nasty bugs, some mild build breakage in Experimental.Outcome may occur as a result. See its commit log for more information. The diff can be viewed at https://github.com/boostorg/outcome/compare/develop?expand=1. Tests pass https://drone.cpp.al/boostorg/outcome/54/1/2 I assume the answer will be I can't merge, but I ask anyway. Niall
On Nov 18, 2022, at 11:03 AM, Niall Douglas via Boost <boost@lists.boost.org> wrote:
On 17/11/2022 14:23, 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
The next deadline: On December 7th, master closes for all changes.
As always, the calendar is at https://www.boost.org/development/ <https://www.boost.org/development/>
Looks like I forgot to merge develop into master branch before the cutoff again. Sigh.
It's all bug fixes since last Boost release, except for a header path rename in Experimental Outcome which might break some code using Experimental Outcome. Here's the changelog:
Enhancements: Update to latest status-code in Experimental.Outcome, which relocates its header files and may cause some end user inclusions to need path changes.
Bug fixes: Latest status-code fixes a number of nasty bugs, some mild build breakage in Experimental.Outcome may occur as a result. See its commit log for more information.
The diff can be viewed at https://github.com/boostorg/outcome/compare/develop?expand=1. Tests pass https://drone.cpp.al/boostorg/outcome/54/1/2
I assume the answer will be I can't merge, but I ask anyway.
Yeah, I think those changes (as a whole) don’t really fit the post-beta “increase stability” criteria. However, if you have specific changes that you want merged, I can look at them. — Marshall
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 request permission to merge some changes from Boost.Locale to master: https://github.com/boostorg/locale/compare/master...Flamefire:locale:warning... (waiting for CI to confirm correctness which was already checked locally, but that is going to take a while) It mostly avoids warnings on MSVC using `-D_SCL_SECURE_NO_WARNINGS` instead of (incomplete) use of `pragma warning(disable : 4996)` as well as a change to the tests to selectively avoid that without that define to make sure it is not required in user code. I also changed CI to reproduce this issue (noticed before only on one of the test runners) And finally a change copied from Boost LWT to avoid message boxes possibly popping up when running the tests with MSVC which leads to timeouts on Appveyor CI. Summary: - New define replacing warning suppression in all compiled sources - Changes to test code to make them more stable - CI only change Hence internal changes only unless users try to run the tests with MSVC which may fail without these changes. Thanks, Alex
Permission to merge this fix to master: https://github.com/boostorg/stl_interfaces/commit/1dc29234347df5aeb3f940d0bf... ? Zach
On Sun, Nov 20, 2022 at 6:29 PM Zach Laine wrote:
Permission to merge this fix to master: https://github.com/boostorg/stl_interfaces/commit/1dc29234347df5aeb3f940d0bf... ?
OK to merge. (Might want to add a unit test which reproduces the problem - e.g. where the previous code would fail because it->x is a const that can't be assigned to) Glen
Hi, I would like to ask permission to merge some changes to Boost.Locale which mostly change only the test. They fix ome spurious test failures during parallel test execution caused by accesses to the same file(s). And also a fix for a warning in a user visible header. There is no change in behavior neither in the the library nor in the tests although one of the tests got a bit refactored to make it easier to read and understand and an additional test added to reproduce the warning (fixed above) in an isolated place. The commits have been cherry-picked from develop to exclude a possibly behavior change introduced as a workaround for rare issue. PR (to master) currently running CI is https://github.com/boostorg/locale/pull/143 Thanks, Alex
On Sat, Nov 26, 2022 at 5:27 AM Alexander Grund wrote:
I would like to ask permission to merge some changes to Boost.Locale which mostly change only the test. [...] PR (to master) currently running CI is https://github.com/boostorg/locale/pull/143
Go ahead. Glen
El 17/11/2022 a las 15:23, Marshall Clow via Boost escribió:
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
The next deadline: On December 7th, master closes for all changes.
As always, the calendar is at https://www.boost.org/development/ <https://www.boost.org/development/>
Hi, requesting permission to merge the following changes to Boost.Unordered: https://github.com/boostorg/unordered/compare/master...develop * Added a couple of CTAD deduction guides missing in Boost 1.81.0 beta 1 * Fixed VS runtime check warnings with /RTCc (issue #151) * Force-inlined some member functions as per issue #168 * Expanded docs * Expanded benchmark section (lib code proper not affected) (Quite extensive) CI tests passing. Best, Joaquín M López Muñoz
On Nov 29, 2022, at 6:58 AM, Joaquin M López Muñoz <joaquinlopezmunoz@gmail.com> wrote:
El 17/11/2022 a las 15:23, Marshall Clow via Boost escribió:
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
The next deadline: On December 7th, master closes for all changes.
As always, the calendar is at https://www.boost.org/development/ <https://www.boost.org/development/>
Hi, requesting permission to merge the following changes to Boost.Unordered:
https://github.com/boostorg/unordered/compare/master...develop
* Added a couple of CTAD deduction guides missing in Boost 1.81.0 beta 1 * Fixed VS runtime check warnings with /RTCc (issue #151) * Force-inlined some member functions as per issue #168 * Expanded docs * Expanded benchmark section (lib code proper not affected)
(Quite extensive) CI tests passing.
Best,
Joaquín M López Muñoz
Go ahead. — Marshall
I'd like to ask for permission to merge the following fix in Boost.URL: Commit: https://github.com/boostorg/url/commit/19b208d53d67e01c5fe44ad85851c239bcd66... Issue: https://github.com/boostorg/url/pull/633 This fixes a bug where ipv4 to string conversion generated the wrong string when the second digit in a number was 0. Em ter., 29 de nov. de 2022 às 12:55, Marshall Clow via Boost < boost@lists.boost.org> escreveu:
On Nov 29, 2022, at 6:58 AM, Joaquin M López Muñoz < joaquinlopezmunoz@gmail.com> wrote:
El 17/11/2022 a las 15:23, Marshall Clow via Boost escribió:
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
The next deadline: On December 7th, master closes for all changes.
As always, the calendar is at https://www.boost.org/development/ <
https://www.boost.org/development/>
Hi, requesting permission to merge the following changes to Boost.Unordered:
https://github.com/boostorg/unordered/compare/master...develop
* Added a couple of CTAD deduction guides missing in Boost 1.81.0 beta 1 * Fixed VS runtime check warnings with /RTCc (issue #151) * Force-inlined some member functions as per issue #168 * Expanded docs * Expanded benchmark section (lib code proper not affected)
(Quite extensive) CI tests passing.
Best,
Joaquín M López Muñoz
Go ahead.
— Marshall
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
-- Alan Freitas https://alandefreitas.github.io/alandefreitas/ <https://github.com/alandefreitas>
On Wednesday, November 30, 2022, Alan de Freitas wrote:
I'd like to ask for permission to merge the following fix in Boost.URL:
Commit: https://github.com/boostorg/url/commit/19b208d53d67e01c5fe44ad85851c2 39bcd66b7c Issue: https://github.com/boostorg/url/pull/633
This fixes a bug where ipv4 to string conversion generated the wrong string when the second digit in a number was 0.
Go ahead.
I would like to ask permission to merge several commits into JSON: Documentation: ca82d81 dropped doc section numbering in files 212c0f2 rewrite conversion docs Silencing warnings: f993635 fix pedantic warnings 719aabd fix conversion warning on 32 bit platforms Fixes to functionality that is new in 1.81: 893df14 fix value_from support for proxy iterators 4d22409 refactor operator>>(istream&, value&) чт, 17 нояб. 2022 г. в 17:23, 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
The next deadline: On December 7th, master closes for all changes.
As always, the calendar is at https://www.boost.org/development/ <https://www.boost.org/development/>
— Marshall
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Missed these two docs commits: 905bf5b fix typo c67d23f 1.81.0 release notes чт, 1 дек. 2022 г. в 22:53, Дмитрий Архипов <grisumbras@gmail.com>:
I would like to ask permission to merge several commits into JSON: Documentation: ca82d81 dropped doc section numbering in files 212c0f2 rewrite conversion docs
Silencing warnings: f993635 fix pedantic warnings 719aabd fix conversion warning on 32 bit platforms
Fixes to functionality that is new in 1.81: 893df14 fix value_from support for proxy iterators 4d22409 refactor operator>>(istream&, value&)
чт, 17 нояб. 2022 г. в 17:23, 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
The next deadline: On December 7th, master closes for all changes.
As always, the calendar is at https://www.boost.org/development/ <https://www.boost.org/development/>
— Marshall
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
On Dec 1, 2022, at 11:53 AM, Дмитрий Архипов via Boost <boost@lists.boost.org> wrote:
I would like to ask permission to merge several commits into JSON: Documentation: ca82d81 dropped doc section numbering in files 212c0f2 rewrite conversion docs
Silencing warnings: f993635 fix pedantic warnings 719aabd fix conversion warning on 32 bit platforms
Fixes to functionality that is new in 1.81: 893df14 fix value_from support for proxy iterators 4d22409 refactor operator>>(istream&, value&)
чт, 17 нояб. 2022 г. в 17:23, 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
The next deadline: On December 7th, master closes for all changes.
As always, the calendar is at https://www.boost.org/development/ <https://www.boost.org/development/>
Go ahead. — Marshall
On 11/17/22 17:23, 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
The next deadline: On December 7th, master closes for all changes.
As always, the calendar is at https://www.boost.org/development/ <https://www.boost.org/development/>
I'd like to ask permission to merge Boost.Filesystem to master: https://github.com/boostorg/filesystem/commit/bd878f47e87222d95d470a57760b11... Added a missing #endif. https://github.com/boostorg/filesystem/commit/8b71cb11a3c60e34ae8f4a52ac44b1... Fixes for compatibility of directory_iterator with older Wine releases and some filesystems on Windows. In particular, in Azure App Service environment. https://github.com/boostorg/filesystem/commit/84f70b0a2a12ffb525b181fc0a3f37... Added a new test for absolute() to verify it works with backslashes and UNC paths. (No functional changes, works as expected.) https://github.com/boostorg/filesystem/commit/c1a48fcdacf2cf06ace147ba532556... Use synchronous IO for handles created in remove_all implementation. Fixes spinning and possible hard errors in directory_iterator implementation on some filesystems on Windows. Complements the fix in 8b71cb11a3c60e34ae8f4a52ac44b1d5fc93d0b0. https://github.com/boostorg/filesystem/commit/48933c5573c5eeba63c103362cad2f... Further improve compatibility with Wine, this time in remove() and remove_all() implementation. https://github.com/boostorg/filesystem/commit/141727b568fad2fecb77b2233a407c... Treat deduplicated files as regular files on Windows. Such files were previously reported as reparse points (which they actually are).
On Saturday, December 3, 2022, Andrey Semashev wrote:
On 11/17/22 17:23, 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
The next deadline: On December 7th, master closes for all changes.
As always, the calendar is at https://www.boost.org/development/ < https://www.boost.org/development/>
I'd like to ask permission to merge Boost.Filesystem to master:
Ok to merge Glen
I would like to ask for permission to merge a small PR with typo & warning fixes. Nothing substantial, just an unused variable warning, plus the obligatory version bump. https://github.com/boostorg/beast/pull/2576 On Sun, Dec 4, 2022 at 3:03 AM Glen Fernandes via Boost < boost@lists.boost.org> wrote:
On Saturday, December 3, 2022, Andrey Semashev wrote:
On 11/17/22 17:23, 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
The next deadline: On December 7th, master closes for all changes.
As always, the calendar is at https://www.boost.org/development/ < https://www.boost.org/development/>
I'd like to ask permission to merge Boost.Filesystem to master:
Ok to merge
Glen
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
On Dec 6, 2022, at 9:54 PM, Klemens Morgenstern via Boost <boost@lists.boost.org> wrote:
I would like to ask for permission to merge a small PR with typo & warning fixes. Nothing substantial, just an unused variable warning, plus the obligatory version bump.
Go ahead. — Marshall
participants (12)
-
Alan de Freitas -
Alexander Grund -
Andrey Semashev -
Glen Fernandes -
Joaquin M López Muñoz -
Klemens Morgenstern -
Marshall Clow -
Niall Douglas -
Peter Dimov -
Stefan Seefeld -
Zach Laine -
Дмитрий Архипов