[release] 1.77.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> Reminder: The master branch closes for the release on Wednesday, August 4th. 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 Thu, Jul 15, 2021 at 7:52 AM 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>
Reminder: The master branch closes for the release on Wednesday, August 4th. Full calendar here: https://www.boost.org/development/ < https://www.boost.org/development/>
— Marshall
Hello Marshall, thank you for managing the releases! I'm requesting permission to merge these two changes to leaf/result.hpp: - A workaround for a GCC bug (github issue 25): https://github.com/boostorg/leaf/commit/e94dab00f8f6ef0d3cbfdf4ec81bf6ff294a... - A bug fix to one of result type's constructors (github issue 26): https://github.com/boostorg/leaf/commit/06a7779699c5bdd2706a52bd86f778e14344... (I've also added several new unit tests and new test configurations.)
On Jul 15, 2021, at 10:27 AM, Emil Dotchevski via Boost <boost@lists.boost.org> wrote:
On Thu, Jul 15, 2021 at 7:52 AM 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>
Reminder: The master branch closes for the release on Wednesday, August 4th. Full calendar here: https://www.boost.org/development/ < https://www.boost.org/development/>
— Marshall
Hello Marshall, thank you for managing the releases! I'm requesting permission to merge these two changes to leaf/result.hpp:
- A workaround for a GCC bug (github issue 25): https://github.com/boostorg/leaf/commit/e94dab00f8f6ef0d3cbfdf4ec81bf6ff294a...
- A bug fix to one of result type's constructors (github issue 26): https://github.com/boostorg/leaf/commit/06a7779699c5bdd2706a52bd86f778e14344...
(I've also added several new unit tests and new test configurations.)
Go ahead. — Marshall
On 15/07/2021 15:52, 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>
Reminder: The master branch closes for the release on Wednesday, August 4th. 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.
I'm just back from annual vacation during which I did not have much access to internet. Before I left I prodded boostorg/outcome master branch to get updated to match standalone master, but it didn't go through, so the beta retains the Outcome from the previous Boost release. Can I get permission to fix this now? I pushed a hand conversion of Outcome master branch to https://github.com/boostorg/outcome/compare/master.future?expand=1 so you can see it (ignore the docs changes, I didn't regenerate those for this hand conversion). As you'll see, the only changes are to build scripting (mostly cmake), and there are a few small bug fixes in the C++. Nothing substantial has changed. Niall
On Jul 16, 2021, at 5:19 AM, Niall Douglas via Boost <boost@lists.boost.org> wrote:
On 15/07/2021 15:52, 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> Reminder: The master branch closes for the release on Wednesday, August 4th. 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.
I'm just back from annual vacation during which I did not have much access to internet. Before I left I prodded boostorg/outcome master branch to get updated to match standalone master, but it didn't go through, so the beta retains the Outcome from the previous Boost release.
Can I get permission to fix this now? I pushed a hand conversion of Outcome master branch to https://github.com/boostorg/outcome/compare/master.future?expand=1 so you can see it (ignore the docs changes, I didn't regenerate those for this hand conversion). As you'll see, the only changes are to build scripting (mostly cmake), and there are a few small bug fixes in the C++. Nothing substantial has changed.
Go ahead. — Marshall
On 16/07/2021 19:37, Marshall Clow wrote:
On Jul 16, 2021, at 5:19 AM, Niall Douglas via Boost <boost@lists.boost.org> wrote:
On 15/07/2021 15:52, 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> Reminder: The master branch closes for the release on Wednesday, August 4th. 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.
I'm just back from annual vacation during which I did not have much access to internet. Before I left I prodded boostorg/outcome master branch to get updated to match standalone master, but it didn't go through, so the beta retains the Outcome from the previous Boost release.
Can I get permission to fix this now? I pushed a hand conversion of Outcome master branch to https://github.com/boostorg/outcome/compare/master.future?expand=1 so you can see it (ignore the docs changes, I didn't regenerate those for this hand conversion). As you'll see, the only changes are to build scripting (mostly cmake), and there are a few small bug fixes in the C++. Nothing substantial has changed.
Go ahead.
Can I get a second permission to fix a bug in Experimental Outcome's status code whereby a status_code wrapped error_code does not compare correctly if the error_code's default condition's category is bespoke? (It's a tiny corner case bug fix) Niall
On Jul 20, 2021, at 8:06 AM, Niall Douglas via Boost <boost@lists.boost.org> wrote:
On 16/07/2021 19:37, Marshall Clow wrote:
On Jul 16, 2021, at 5:19 AM, Niall Douglas via Boost <boost@lists.boost.org> wrote:
On 15/07/2021 15:52, 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> Reminder: The master branch closes for the release on Wednesday, August 4th. 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.
I'm just back from annual vacation during which I did not have much access to internet. Before I left I prodded boostorg/outcome master branch to get updated to match standalone master, but it didn't go through, so the beta retains the Outcome from the previous Boost release.
Can I get permission to fix this now? I pushed a hand conversion of Outcome master branch to https://github.com/boostorg/outcome/compare/master.future?expand=1 so you can see it (ignore the docs changes, I didn't regenerate those for this hand conversion). As you'll see, the only changes are to build scripting (mostly cmake), and there are a few small bug fixes in the C++. Nothing substantial has changed.
Go ahead.
Can I get a second permission to fix a bug in Experimental Outcome's status code whereby a status_code wrapped error_code does not compare correctly if the error_code's default condition's category is bespoke?
(It's a tiny corner case bug fix)
Has it been fixed on develop? Have the tests cycled, and are you happy with the results? If so, then you can merge to master. If not, let’s do that first. — Marshall
On 7/15/21 5:52 PM, 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>
Reminder: The master branch closes for the release on Wednesday, August 4th. Full calendar here: https://www.boost.org/development/ <https://www.boost.org/development/>
I would like to merge the following changes to master: https://github.com/boostorg/filesystem/commit/d41885883907ff91f16b09a5cda332... Fixes a regression in path::lexically_normal as it doesn't convert root directory to preferred separator. https://github.com/boostorg/log/commit/9fe832c344e645d82a902a8d465e0b1e8ef6b... Fixes incorrect accounting for the initial size of a log file opened for appending.
On Jul 20, 2021, at 3:17 AM, Andrey Semashev via Boost <boost@lists.boost.org> wrote:
On 7/15/21 5:52 PM, 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> Reminder: The master branch closes for the release on Wednesday, August 4th. Full calendar here: https://www.boost.org/development/ <https://www.boost.org/development/>
I would like to merge the following changes to master:
https://github.com/boostorg/filesystem/commit/d41885883907ff91f16b09a5cda332...
Fixes a regression in path::lexically_normal as it doesn't convert root directory to preferred separator.
https://github.com/boostorg/log/commit/9fe832c344e645d82a902a8d465e0b1e8ef6b...
Fixes incorrect accounting for the initial size of a log file opened for appending.
When you’re happy with the test results, go ahead. — Marshall
W dniu 15.07.2021 o 16:52, 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. See <https://github.com/boostorg/wiki/wiki/Releases%3A-Beta-Merge-Policy>
Reminder: The master branch closes for the release on Wednesday, August 4th. Full calendar here: https://www.boost.org/development/ <https://www.boost.org/development/> Hi Marshall,
I'd like to request a merge for the following fixes: https://github.com/boostorg/geometry/pull/886/files https://github.com/boostorg/geometry/commit/46e3d9231c2353b323796b6423f13cd6... Adam
On Jul 20, 2021, at 3:52 AM, Adam Wulkiewicz via Boost <boost@lists.boost.org> wrote:
W dniu 15.07.2021 o 16:52, 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. See <https://github.com/boostorg/wiki/wiki/Releases%3A-Beta-Merge-Policy>
Reminder: The master branch closes for the release on Wednesday, August 4th. Full calendar here: https://www.boost.org/development/ <https://www.boost.org/development/> Hi Marshall,
I'd like to request a merge for the following fixes: https://github.com/boostorg/geometry/pull/886/files https://github.com/boostorg/geometry/commit/46e3d9231c2353b323796b6423f13cd6...
When you’re happy with the test results, go ahead. — Marshall
On 7/15/21 5:52 PM, 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>
Reminder: The master branch closes for the release on Wednesday, August 4th. Full calendar here: https://www.boost.org/development/ <https://www.boost.org/development/>
I would like to merge the following changes to master: https://github.com/boostorg/filesystem/commit/87d3c1fd8ab94c188719681ee0bb8f... Fixes weakly_canonical on Windows when the input path contains non-existing directories. https://github.com/boostorg/core/commit/9f0b97c80bfec9cd1088cf9d4cc0326ebbe9... Minor fix in CI config file.
On 7/28/21 9:33 PM, Andrey Semashev wrote:
On 7/15/21 5:52 PM, 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>
Reminder: The master branch closes for the release on Wednesday, August 4th. Full calendar here: https://www.boost.org/development/ <https://www.boost.org/development/>
I would like to merge the following changes to master:
https://github.com/boostorg/filesystem/commit/87d3c1fd8ab94c188719681ee0bb8f...
Fixes weakly_canonical on Windows when the input path contains non-existing directories.
https://github.com/boostorg/core/commit/9f0b97c80bfec9cd1088cf9d4cc0326ebbe9...
Minor fix in CI config file.
Ping?
On Jul 28, 2021, at 11:33 AM, Andrey Semashev via Boost <boost@lists.boost.org> wrote:
On 7/15/21 5:52 PM, 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> Reminder: The master branch closes for the release on Wednesday, August 4th. Full calendar here: https://www.boost.org/development/ <https://www.boost.org/development/>
I would like to merge the following changes to master:
https://github.com/boostorg/filesystem/commit/87d3c1fd8ab94c188719681ee0bb8f...
Fixes weakly_canonical on Windows when the input path contains non-existing directories.
https://github.com/boostorg/core/commit/9f0b97c80bfec9cd1088cf9d4cc0326ebbe9...
Minor fix in CI config file.
If you’re happy with the test results, then go ahead. — Marshall
participants (5)
-
Adam Wulkiewicz -
Andrey Semashev -
Emil Dotchevski -
Marshall Clow -
Niall Douglas