Re: [boost] [release] 1.77.0 post-beta merges

On Jul 20, 2021, at 8:06 AM, Niall Douglas via Boost wrote:

On 16/07/2021 19:37, Marshall Clow wrote:

...

On Jul 16, 2021, at 5:19 AM, Niall Douglas via Boost 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