On 17/03/2022 18:30, Marshall Clow via Boost wrote:

On Mar 16, 2022, at 1:03 PM, Niall Douglas via Boost wrote:

...

On 16/03/2022 17:12, 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>

I'd like to merge Outcome develop into master.

There have been nothing but bugfixes and docs changes since last Boost release.

Develop branch is passing https://www.boost.org/development/tests/develop/developer/outcome.html

Niall -

In the future, I’d appreciate something more descriptive than “nothing but bug fixes”.

I can dig it out of the commit history on develop (which I did), and those all look like bug fixes, with the exception of https://github.com/boostorg/outcome/commit/05ed97720204ff734475c2b47e600d382... https://github.com/boostorg/outcome/commit/05ed97720204ff734475c2b47e600d382...

Fair enough, may I suggest that I merge the commit immediately before 05ed977 to master? I'm sorry that I didn't get to merging develop to master before the beta cutoff. Lots going on in private life right now, it slipped my mind. Niall

On 05/04/2022 18:06, Marshall Clow via Boost wrote:

On Mar 19, 2022, at 9:55 AM, John Maddock via Boost wrote:

...

On 16/03/2022 17:12, 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> If possible I'd like to merge the following low-risk Multiprecision bug-fix: https://github.com/boostorg/multiprecision/pull/440/files

...

P.S Doc changes and test changes do NOT require release manager approval to be merged. Just a friendly heads up, that I've just updated the Math lib docs in master :)

Thanks, John. Missed this first time around; sorry. No problem, merged, thanks!

Go ahead.

— Marshall

_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

On Apr 6, 2022, at 12:56 PM, Andrey Semashev via Boost wrote:

On 3/16/22 20:12, 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, April 6th. 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/aeb5318cd0a155c5d18e6b190024c2...

It silences a bogus gcc warning.

CI tests have passed.

Go ahead. — Marshall