[release] 1.78.0 post-beta merges
The master branch is is now open for post-beta merges, but only as described in the Post-Beta Merge Policy. See <https://github.com/boostorg/wiki/wiki/Releases%3A-Beta-Merge-Policy <https://github.com/boostorg/wiki/wiki/Releases%3A-Beta-Merge-Policy>> Reminder: The master branch closes for the release on Wednesday, December 1st. Full calendar here: https://www.boost.org/development/ <https://www.boost.org/development/> — Marshall P.S Doc changes and test changes do NOT require release manager approval to be merged.
On 11/12/21 04:15, Marshall Clow via Boost wrote:
The master branch is is now open for post-beta merges, but only as described in the Post-Beta Merge Policy. See <https://github.com/boostorg/wiki/wiki/Releases%3A-Beta-Merge-Policy <https://github.com/boostorg/wiki/wiki/Releases%3A-Beta-Merge-Policy>>
Reminder: The master branch closes for the release on Wednesday, December 1st. Full calendar here: https://www.boost.org/development/ <https://www.boost.org/development/>
I would like to merge Boost.Filesystem develop to master: https://github.com/boostorg/filesystem/compare/master...develop Break down by commits: https://github.com/boostorg/filesystem/commit/d13461be0f8fafe2d63b87141bcd14... https://github.com/boostorg/filesystem/commit/ecbab750b2c49b3d5805dbd3f4c285... https://github.com/boostorg/filesystem/commit/0d413a5e4fbdb6c7c1ac9b54ae5298... In v4, path appends (operator/, operator/=, path::append) now recognize root name and root directory in the appended paths and behave closer to C++17. v3 path appends are unchanged. https://github.com/boostorg/filesystem/commit/cc763cb48efea3dac897752d403d5b... absolute() reworked to account for the v4 path appends change. It also fixes incorrect behavior for v3, when the input path was already absolute - the old implementation used to add a root name from the base path in this case. https://github.com/boostorg/filesystem/commit/37bfbbb376caac04e222af65baa1ed... Updated canonical/weakly_canonical to also accommodate changed v4 path appends. https://github.com/boostorg/filesystem/commit/0aee13c162ccfe88fa3415791bd312... This completes v4 path appends change by adding a trailing separator when the appended path is empty, like C++17. https://github.com/boostorg/filesystem/commit/0307f58a8b2176f6709d3d7df33924... Update v4 path::lexically_normal to avoid appending the trailing dot filename when the original path ends with a separator. This complements the earlier change in v4 path::filename and path::iterator (which is already in master) to omit the trailing dot and also matches C++17. Also, for v3 and v4 the directory separators in the root name are now converted to preferred separators. This matches C++17 and improves behavior wrt. UNC paths on Windows. https://github.com/boostorg/filesystem/commit/7fc42097cf7977fb4d5b908c4a3090... Fixes potential linking errors in case if the compiler is set to preserve unused inline functions. This was reported in https://github.com/boostorg/filesystem/issues/215. For clarity, Boost.Filesystem v3 is currently the default and v4 is the new (experimental) version that aims for better compatibility with C++17. All changes have passed the CI tests.
On 11/12/21 04:15, Marshall Clow via Boost wrote:
The master branch is is now open for post-beta merges, but only as described in the Post-Beta Merge Policy. See <https://github.com/boostorg/wiki/wiki/Releases%3A-Beta-Merge-Policy <https://github.com/boostorg/wiki/wiki/Releases%3A-Beta-Merge-Policy>>
Reminder: The master branch closes for the release on Wednesday, December 1st. Full calendar here: https://www.boost.org/development/ <https://www.boost.org/development/>
I'd like to merge this commit into Boost.Log master: https://github.com/boostorg/log/commit/036bd4fffd9b66041daa1dc52cded8d807f2b... It removes a workaround for a missing dependency in Boost.ASIO CMakeLists.txt. The workaround is no longer needed. CI tests passed.
On Nov 13, 2021, at 12:49 AM, Andrey Semashev via Boost <boost@lists.boost.org> wrote:
On 11/12/21 04:15, Marshall Clow via Boost wrote:
The master branch is is now open for post-beta merges, but only as described in the Post-Beta Merge Policy. See <https://github.com/boostorg/wiki/wiki/Releases%3A-Beta-Merge-Policy <https://github.com/boostorg/wiki/wiki/Releases%3A-Beta-Merge-Policy>>
Reminder: The master branch closes for the release on Wednesday, December 1st. Full calendar here: https://www.boost.org/development/ <https://www.boost.org/development/>
I'd like to merge this commit into Boost.Log master:
https://github.com/boostorg/log/commit/036bd4fffd9b66041daa1dc52cded8d807f2b...
It removes a workaround for a missing dependency in Boost.ASIO CMakeLists.txt. The workaround is no longer needed.
CI tests passed.
Go ahead. — Marshall
On 12. Nov 2021, at 02:15, Marshall Clow via Boost <boost@lists.boost.org> wrote:
The master branch is is now open for post-beta merges, but only as described in the Post-Beta Merge Policy. See <https://github.com/boostorg/wiki/wiki/Releases%3A-Beta-Merge-Policy <https://github.com/boostorg/wiki/wiki/Releases%3A-Beta-Merge-Policy>>
I would like to merge the following fixes to master https://github.com/boostorg/histogram/commit/904cc3cbf2cd8f5d6a443afdc5923e9... This just capitalises the name "histogram" in the meta json. https://github.com/boostorg/histogram/commit/7ec89f45f6ecbb76e4932a91bd55258... This is a fix for users that include windows.h, which has the line `#define small char` that conflicts with variable and method names in the library. The change deprecates the interface that causes the problem and introduces a new conflict-free interface. The deprecated interface is further ifdef'ed to be excluded when "small" is defined in the preprocessing stage. The change does not break the code for users that did not run into this problem, and it fixes the broken library for those that did. Best regards, Hans
On Nov 13, 2021, at 4:34 AM, Hans Dembinski <hans.dembinski@gmail.com> wrote:
On 12. Nov 2021, at 02:15, Marshall Clow via Boost <boost@lists.boost.org> wrote:
The master branch is is now open for post-beta merges, but only as described in the Post-Beta Merge Policy. See <https://github.com/boostorg/wiki/wiki/Releases%3A-Beta-Merge-Policy <https://github.com/boostorg/wiki/wiki/Releases%3A-Beta-Merge-Policy>>
I would like to merge the following fixes to master
https://github.com/boostorg/histogram/commit/904cc3cbf2cd8f5d6a443afdc5923e9...
This just capitalises the name "histogram" in the meta json.
https://github.com/boostorg/histogram/commit/7ec89f45f6ecbb76e4932a91bd55258...
This is a fix for users that include windows.h, which has the line `#define small char` that conflicts with variable and method names in the library. The change deprecates the interface that causes the problem and introduces a new conflict-free interface. The deprecated interface is further ifdef'ed to be excluded when "small" is defined in the preprocessing stage. The change does not break the code for users that did not run into this problem, and it fixes the broken library for those that did.
Go ahead. — Marshall
On 12/11/2021 2:15, Marshall Clow via Boost wrote:
The master branch is is now open for post-beta merges, but only as described in the Post-Beta Merge Policy. See <https://github.com/boostorg/wiki/wiki/Releases%3A-Beta-Merge-Policy <https://github.com/boostorg/wiki/wiki/Releases%3A-Beta-Merge-Policy>>
Reminder: The master branch closes for the release on Wednesday, December 1st. Full calendar here: https://www.boost.org/development/ <https://www.boost.org/development/>
— Marshall
Hi, I'd like to merge the following commits (already cycled in develop): Interprocess: https://github.com/boostorg/interprocess/commit/85786848f0c659173cf0f27eba7f... Move: https://github.com/boostorg/move/commit/a51c5cc218a9f02331227db6f8409f8db513... Best, Ion
On Nov 14, 2021, at 10:38 AM, Ion Gaztañaga via Boost <boost@lists.boost.org> wrote:
On 12/11/2021 2:15, Marshall Clow via Boost wrote:
The master branch is is now open for post-beta merges, but only as described in the Post-Beta Merge Policy. See <https://github.com/boostorg/wiki/wiki/Releases%3A-Beta-Merge-Policy <https://github.com/boostorg/wiki/wiki/Releases%3A-Beta-Merge-Policy>> Reminder: The master branch closes for the release on Wednesday, December 1st. Full calendar here: https://www.boost.org/development/ <https://www.boost.org/development/> — Marshall
Hi,
I'd like to merge the following commits (already cycled in develop):
Interprocess:
https://github.com/boostorg/interprocess/commit/85786848f0c659173cf0f27eba7f...
Move:
https://github.com/boostorg/move/commit/a51c5cc218a9f02331227db6f8409f8db513...
Go ahead.. — Marshall
On 11/12/21 04:15, Marshall Clow via Boost wrote:
The master branch is is now open for post-beta merges, but only as described in the Post-Beta Merge Policy. See <https://github.com/boostorg/wiki/wiki/Releases%3A-Beta-Merge-Policy <https://github.com/boostorg/wiki/wiki/Releases%3A-Beta-Merge-Policy>>
Reminder: The master branch closes for the release on Wednesday, December 1st. Full calendar here: https://www.boost.org/development/ <https://www.boost.org/development/>
I would like to merge the following commits to Boost.Atomic master: https://github.com/boostorg/atomic/commit/71e9ed3417957e3e5767c064bc9e196b50... https://github.com/boostorg/atomic/commit/ead065fc4781626185c1c95874a6928909... Fixes compilation with VS2015 prior to Update 3. https://github.com/boostorg/atomic/commit/2069feeb792bc4017f86b2a89051279f2d... CI config fix. CI tests have passed.
On Tue, Nov 16, 2021 at 4:18 AM Andrey Semashev via Boost <boost@lists.boost.org> wrote:
I would like to merge the following commits to Boost.Atomic master:
https://github.com/boostorg/atomic/commit/71e9ed3417957e3e5767c064bc9e196b50... https://github.com/boostorg/atomic/commit/ead065fc4781626185c1c95874a6928909...
Fixes compilation with VS2015 prior to Update 3.
https://github.com/boostorg/atomic/commit/2069feeb792bc4017f86b2a89051279f2d...
CI config fix.
CI tests have passed.
Go ahead. Glen
Marshall Clow wrote:
The master branch is is now open for post-beta merges, but only as described in the Post-Beta Merge Policy. See <https://github.com/boostorg/wiki/wiki/Releases%3A-Beta-Merge-Policy <https://github.com/boostorg/wiki/wiki/Releases%3A-Beta-Merge-Policy>>
Reminder: The master branch closes for the release on Wednesday, December 1st. Full calendar here: https://www.boost.org/development/ <https://www.boost.org/development/>
I'd like to merge the following commit to master: https://github.com/boostorg/describe/commit/1fa144623dde8322fb3e84acf03b50ea... This is PR #24: https://github.com/boostorg/describe/pull/24 that fixes a warning under Clang: https://github.com/boostorg/describe/issues/23
On Nov 17, 2021, at 4:10 AM, Peter Dimov via Boost <boost@lists.boost.org> wrote:
Marshall Clow wrote:
The master branch is is now open for post-beta merges, but only as described in the Post-Beta Merge Policy. See <https://github.com/boostorg/wiki/wiki/Releases%3A-Beta-Merge-Policy <https://github.com/boostorg/wiki/wiki/Releases%3A-Beta-Merge-Policy>>
Reminder: The master branch closes for the release on Wednesday, December 1st. Full calendar here: https://www.boost.org/development/ <https://www.boost.org/development/>
I'd like to merge the following commit to master:
https://github.com/boostorg/describe/commit/1fa144623dde8322fb3e84acf03b50ea...
This is PR #24:
https://github.com/boostorg/describe/pull/24
that fixes a warning under Clang:
If you’re happy with the test results, go ahead. — Marshall
On 11/12/21 04:15, Marshall Clow via Boost wrote:
The master branch is is now open for post-beta merges, but only as described in the Post-Beta Merge Policy. See <https://github.com/boostorg/wiki/wiki/Releases%3A-Beta-Merge-Policy <https://github.com/boostorg/wiki/wiki/Releases%3A-Beta-Merge-Policy>>
Reminder: The master branch closes for the release on Wednesday, December 1st. Full calendar here: https://www.boost.org/development/ <https://www.boost.org/development/>
I'd like to merge the following commits to Boost.Filesystem master: https://github.com/boostorg/filesystem/commit/18a8a3430ddd532bf78494817b193b... Adds support for deleting read-only files on Windows. Previously, remove() would fail with an error in such a case. https://github.com/boostorg/filesystem/commit/3ccf3d8afd00d1e58a2c8f906ee7b4... Return -1 from remove_all() in case of errors, similar to C++17 std::filesystem. https://github.com/boostorg/filesystem/commit/0f695acdf96ac1e3664085e1d4813f... Cosmetics - replaced magic constant with INVALID_FILE_ATTRIBUTES. CI tests have passed.
On Nov 18, 2021, at 7:54 AM, Andrey Semashev via Boost <boost@lists.boost.org> wrote:
On 11/12/21 04:15, Marshall Clow via Boost wrote:
The master branch is is now open for post-beta merges, but only as described in the Post-Beta Merge Policy. See <https://github.com/boostorg/wiki/wiki/Releases%3A-Beta-Merge-Policy <https://github.com/boostorg/wiki/wiki/Releases%3A-Beta-Merge-Policy>>
Reminder: The master branch closes for the release on Wednesday, December 1st. Full calendar here: https://www.boost.org/development/ <https://www.boost.org/development/>
I'd like to merge the following commits to Boost.Filesystem master:
https://github.com/boostorg/filesystem/commit/18a8a3430ddd532bf78494817b193b...
Adds support for deleting read-only files on Windows. Previously, remove() would fail with an error in such a case.
https://github.com/boostorg/filesystem/commit/3ccf3d8afd00d1e58a2c8f906ee7b4...
Return -1 from remove_all() in case of errors, similar to C++17 std::filesystem.
https://github.com/boostorg/filesystem/commit/0f695acdf96ac1e3664085e1d4813f...
Cosmetics - replaced magic constant with INVALID_FILE_ATTRIBUTES.
CI tests have passed.
Go ahead. — Marshall
Marshall Clow wrote:
The master branch is is now open for post-beta merges, but only as described in the Post-Beta Merge Policy. See <https://github.com/boostorg/wiki/wiki/Releases%3A-Beta-Merge-Policy <https://github.com/boostorg/wiki/wiki/Releases%3A-Beta-Merge-Policy>>
I'd like to merge the following commit to master: https://github.com/boostorg/mp11/commit/a4d7c46670dc7b354c695e8c2c84b2dc44cd... It fixes the following CUDA-specific issue: https://github.com/boostorg/mp11/issues/68
On Thu, Nov 18, 2021 at 8:04 PM Peter Dimov via Boost <boost@lists.boost.org> wrote:
I'd like to merge the following commit to master:
https://github.com/boostorg/mp11/commit/a4d7c46670dc7b354c695e8c2c84b2dc44cd...
It fixes the following CUDA-specific issue:
Good to merge. Glen
On Thu, Nov 11, 2021 at 5:16 PM Marshall Clow via Boost < boost@lists.boost.org> wrote:
The master branch is is now open for post-beta merges, but only as
described in the Post-Beta Merge Policy.
See <https://github.com/boostorg/wiki/wiki/Releases%3A-Beta-Merge-Policy < https://github.com/boostorg/wiki/wiki/Releases%3A-Beta-Merge-Policy>>
Requesting permission to merge in documentation and examples update to Boost LEAF (no changes to the library itself).
On Nov 18, 2021, at 5:48 PM, Emil Dotchevski via Boost <boost@lists.boost.org> wrote:
On Thu, Nov 11, 2021 at 5:16 PM Marshall Clow via Boost < boost@lists.boost.org> wrote:
The master branch is is now open for post-beta merges, but only as
described in the Post-Beta Merge Policy.
See <https://github.com/boostorg/wiki/wiki/Releases%3A-Beta-Merge-Policy < https://github.com/boostorg/wiki/wiki/Releases%3A-Beta-Merge-Policy>>
Requesting permission to merge in documentation and examples update to Boost LEAF (no changes to the library itself).
You don’t need permission for doc changes. Test changes are fine, too. — Marshall
Permission to merge B2 4.7.2 < https://github.com/boostorg/build/commit/aaa95bba19a7acb07badb1929737c67583b...
-- -- René Ferdinand Rivera Morell -- Don't Assume Anything -- No Supone Nada -- Robot Dreams - http://robot-dreams.net
On Fri, Nov 19, 2021 at 7:22 AM René Ferdinand Rivera Morell < grafikrobot@gmail.com> wrote:
Permission to merge B2 4.7.2 < https://github.com/boostorg/build/commit/aaa95bba19a7acb07badb1929737c67583b...
FYI.. Corresponding release notes PR < https://github.com/boostorg/website/pull/652> -- -- René Ferdinand Rivera Morell -- Don't Assume Anything -- No Supone Nada -- Robot Dreams - http://robot-dreams.net
On 12/11/2021 01:15, Marshall Clow via Boost wrote:
The master branch is is now open for post-beta merges, but only as described in the Post-Beta Merge Policy. See <https://github.com/boostorg/wiki/wiki/Releases%3A-Beta-Merge-Policy <https://github.com/boostorg/wiki/wiki/Releases%3A-Beta-Merge-Policy>>
Permission to merge develop into master for Outcome. Changes: - Workaround ICE in Experimental.Outcome on GCCs before 8. - Support Boost CI. Niall
On Thu, Nov 11, 2021 at 5:16 PM Marshall Clow via Boost < boost@lists.boost.org> wrote:
The master branch is is now open for post-beta merges, but only as
described in the Post-Beta Merge Policy.
See <https://github.com/boostorg/wiki/wiki/Releases%3A-Beta-Merge-Policy < https://github.com/boostorg/wiki/wiki/Releases%3A-Beta-Merge-Policy>>
I would like to merge this change, which integrates a pull request from vector-of-bool: https://github.com/boostorg/leaf/commit/a24b2b08350988671eac5bf942f6bac1d5fb...
On Sun, Nov 21, 2021 at 1:21 PM Emil Dotchevski via Boost <boost@lists.boost.org> wrote:
I would like to merge this change, which integrates a pull request from vector-of-bool: https://github.com/boostorg/leaf/commit/a24b2b08350988671eac5bf942f6bac1d5fb...
OK to merge.
On Thu, Nov 11, 2021 at 5:16 PM Marshall Clow via Boost < boost@lists.boost.org> wrote:
The master branch is is now open for post-beta merges, but only as
described in the Post-Beta Merge Policy.
See <https://github.com/boostorg/wiki/wiki/Releases%3A-Beta-Merge-Policy < https://github.com/boostorg/wiki/wiki/Releases%3A-Beta-Merge-Policy>>
I'd like to merge this commit: https://github.com/boostorg/leaf/commit/35295d2ca0c683fbd1bab35acf8a88d7d9b1... It adds two new unit tests, expands on an existing test program, and fixes the relevant bug.
On 11/12/21 04:15, Marshall Clow via Boost wrote:
The master branch is is now open for post-beta merges, but only as described in the Post-Beta Merge Policy. See <https://github.com/boostorg/wiki/wiki/Releases%3A-Beta-Merge-Policy <https://github.com/boostorg/wiki/wiki/Releases%3A-Beta-Merge-Policy>>
Reminder: The master branch closes for the release on Wednesday, December 1st. Full calendar here: https://www.boost.org/development/ <https://www.boost.org/development/>
I would like to merge the following commit to Boost.Filesystem master: https://github.com/boostorg/filesystem/commit/fa53749ac7679ec767f044f4f92d4c... Fixes a potential memory leak with MSVC and compatible compilers in release builds, if Boost.Filesystem shared library is repeatedly loaded/unloaded.
On 11/22/21 17:31, Andrey Semashev wrote:
On 11/12/21 04:15, Marshall Clow via Boost wrote:
The master branch is is now open for post-beta merges, but only as described in the Post-Beta Merge Policy. See <https://github.com/boostorg/wiki/wiki/Releases%3A-Beta-Merge-Policy <https://github.com/boostorg/wiki/wiki/Releases%3A-Beta-Merge-Policy>>
Reminder: The master branch closes for the release on Wednesday, December 1st. Full calendar here: https://www.boost.org/development/ <https://www.boost.org/development/>
I would like to merge the following commit to Boost.Filesystem master:
https://github.com/boostorg/filesystem/commit/fa53749ac7679ec767f044f4f92d4c...
Fixes a potential memory leak with MSVC and compatible compilers in release builds, if Boost.Filesystem shared library is repeatedly loaded/unloaded.
Forgot to mention that CI tests have passed.
On Monday, November 22, 2021, Andrey Semashev via Boost < boost@lists.boost.org> wrote:
I would like to merge the following commit to Boost.Filesystem master:
https://github.com/boostorg/filesystem/commit/ fa53749ac7679ec767f044f4f92d4caa26ec87f4
Fixes a potential memory leak with MSVC and compatible compilers in release builds, if Boost.Filesystem shared library is repeatedly loaded/unloaded.
Go ahead.
On Thu, Nov 11, 2021 at 5:16 PM Marshall Clow via Boost < boost@lists.boost.org> wrote:
The master branch is is now open for post-beta merges, but only as
described in the Post-Beta Merge Policy.
See <https://github.com/boostorg/wiki/wiki/Releases%3A-Beta-Merge-Policy < https://github.com/boostorg/wiki/wiki/Releases%3A-Beta-Merge-Policy>>
I'd like to merge this bugfix, it enables error handlers to catch abstract exception types: https://github.com/boostorg/leaf/commit/084601667150d8512f041f851fdae05d015f... .
On Nov 24, 2021, at 10:01 AM, Emil Dotchevski via Boost <boost@lists.boost.org> wrote:
On Thu, Nov 11, 2021 at 5:16 PM Marshall Clow via Boost < boost@lists.boost.org> wrote:
The master branch is is now open for post-beta merges, but only as
described in the Post-Beta Merge Policy.
See <https://github.com/boostorg/wiki/wiki/Releases%3A-Beta-Merge-Policy < https://github.com/boostorg/wiki/wiki/Releases%3A-Beta-Merge-Policy>>
I'd like to merge this bugfix, it enables error handlers to catch abstract exception types: https://github.com/boostorg/leaf/commit/084601667150d8512f041f851fdae05d015f...
Once you’re happy with the test results (I see you committed it to develop an hour ago), you can go ahead. — Marshall
On 12/11/2021 01:15, Marshall Clow via Boost wrote:
The master branch is is now open for post-beta merges, but only as described in the Post-Beta Merge Policy. See <https://github.com/boostorg/wiki/wiki/Releases%3A-Beta-Merge-Policy <https://github.com/boostorg/wiki/wiki/Releases%3A-Beta-Merge-Policy>>
Reminder: The master branch closes for the release on Wednesday, December 1st. Full calendar here: https://www.boost.org/development/ <https://www.boost.org/development/>
There are some minor changes to Boost.Config for msvc-14.3: https://github.com/boostorg/config/pull/411 now in develop with green CI etc. I rather doubt these changes will effect anyone directly right at this minute, but I thought I'd ask whether we want these to go in the next release or no. Cheers, John. -- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus
On Nov 24, 2021, at 11:00 AM, John Maddock via Boost <boost@lists.boost.org> wrote:
On 12/11/2021 01:15, Marshall Clow via Boost wrote:
The master branch is is now open for post-beta merges, but only as described in the Post-Beta Merge Policy. See <https://github.com/boostorg/wiki/wiki/Releases%3A-Beta-Merge-Policy <https://github.com/boostorg/wiki/wiki/Releases%3A-Beta-Merge-Policy>>
Reminder: The master branch closes for the release on Wednesday, December 1st. Full calendar here: https://www.boost.org/development/ <https://www.boost.org/development/>
There are some minor changes to Boost.Config for msvc-14.3: https://github.com/boostorg/config/pull/411 now in develop with green CI etc.
I rather doubt these changes will effect anyone directly right at this minute, but I thought I'd ask whether we want these to go in the next release or no.
Cheers, John.
These look pretty low-risk to me. Go ahead. — Marshall
On 29/11/2021 16:26, Marshall Clow via Boost wrote:
On Nov 24, 2021, at 11:00 AM, John Maddock via Boost <boost@lists.boost.org> wrote:
On 12/11/2021 01:15, Marshall Clow via Boost wrote:
The master branch is is now open for post-beta merges, but only as described in the Post-Beta Merge Policy. See <https://github.com/boostorg/wiki/wiki/Releases%3A-Beta-Merge-Policy <https://github.com/boostorg/wiki/wiki/Releases%3A-Beta-Merge-Policy>>
Reminder: The master branch closes for the release on Wednesday, December 1st. Full calendar here: https://www.boost.org/development/ <https://www.boost.org/development/> There are some minor changes to Boost.Config for msvc-14.3: https://github.com/boostorg/config/pull/411 now in develop with green CI etc.
I rather doubt these changes will effect anyone directly right at this minute, but I thought I'd ask whether we want these to go in the next release or no.
Cheers, John. These look pretty low-risk to me. Go ahead.
Done! Cheers, John. -- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus
W dniu 12.11.2021 o 02:15, Marshall Clow via Boost pisze:
The master branch is is now open for post-beta merges, but only as described in the Post-Beta Merge Policy. I'd like to ask for permission to merge a trivial fix (the first file): https://github.com/boostorg/geometry/compare/master...develop
The rest are changes in tests. Adam
On Nov 29, 2021, at 7:05 AM, Adam Wulkiewicz via Boost <boost@lists.boost.org> wrote:
W dniu 12.11.2021 o 02:15, Marshall Clow via Boost pisze:
The master branch is is now open for post-beta merges, but only as described in the Post-Beta Merge Policy. I'd like to ask for permission to merge a trivial fix (the first file): https://github.com/boostorg/geometry/compare/master...develop
The rest are changes in tests.
Go ahead. — Marshall
On Thu, Nov 11, 2021 at 5:16 PM Marshall Clow via Boost < boost@lists.boost.org> wrote:
The master branch is is now open for post-beta merges, but only as
described in the Post-Beta Merge Policy.
See <https://github.com/boostorg/wiki/wiki/Releases%3A-Beta-Merge-Policy < https://github.com/boostorg/wiki/wiki/Releases%3A-Beta-Merge-Policy>>
I'd like to merge to master this LEAF commit: https://github.com/boostorg/leaf/commit/5cf3ed38ab2b0fbb5b0c736000f919fe0aec.... GHA is all green. It allows class enums to be printed in diagnostic information messages.
On Nov 29, 2021, at 6:45 PM, Emil Dotchevski via Boost <boost@lists.boost.org> wrote:
On Thu, Nov 11, 2021 at 5:16 PM Marshall Clow via Boost < boost@lists.boost.org> wrote:
The master branch is is now open for post-beta merges, but only as
described in the Post-Beta Merge Policy.
See <https://github.com/boostorg/wiki/wiki/Releases%3A-Beta-Merge-Policy < https://github.com/boostorg/wiki/wiki/Releases%3A-Beta-Merge-Policy>>
I'd like to merge to master this LEAF commit: https://github.com/boostorg/leaf/commit/5cf3ed38ab2b0fbb5b0c736000f919fe0aec.... GHA is all green.
It allows class enums to be printed in diagnostic information messages.
Emil — This doesn’t really look like a bug fix to me. It looks like a new feature; but it’s a really minor enhancement. If you’re sure that it won’t cause any problems, go ahead. If you’re not sure, then let’s wait for next release. — Marshall
participants (11)
-
Adam Wulkiewicz -
Andrey Semashev -
Emil Dotchevski -
Glen Fernandes -
Hans Dembinski -
Ion Gaztañaga -
John Maddock -
Marshall Clow -
Niall Douglas -
Peter Dimov -
René Ferdinand Rivera Morell