[release] 1.79.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, April 6th. 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 Wed, Mar 16, 2022 at 12:13 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.
I'd like to merge B2 4.8.0 to master. There are a pair of changes that resolve some missing files during installation: Add .ipp extension to header scanning and a valid C++ file. -- Jim King Fix missing install targets when build=no is in source target usage requirements. -- Dmitry Arkhipov Other fixes mentioned in the release notes: < https://github.com/bfgroup/b2/releases/tag/4.8.0> -- -- René Ferdinand Rivera Morell -- Don't Assume Anything -- No Supone Nada -- Robot Dreams - http://robot-dreams.net
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
On Mar 16, 2022, at 1:03 PM, Niall Douglas via Boost <boost@lists.boost.org> 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/05ed97720204ff734475c2b47e600d382e7e3a70> — Marshall
On 17/03/2022 18:30, Marshall Clow via Boost wrote:
On Mar 16, 2022, at 1:03 PM, Niall Douglas via Boost <boost@lists.boost.org> 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/05ed97720204ff734475c2b47e600d382e7e3a70>
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 Mar 17, 2022, at 11:44 AM, Niall Douglas via Boost <boost@lists.boost.org> wrote:
On 17/03/2022 18:30, Marshall Clow via Boost wrote:
On Mar 16, 2022, at 1:03 PM, Niall Douglas via Boost <boost@lists.boost.org> 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... <https://github.com/boostorg/outcome/commit/05ed97720204ff734475c2b47e600d382e7e3a70>>
Fair enough, may I suggest that I merge the commit immediately before 05ed977 to master?
That would be fine. Thanks. — Marshall
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.
On Mar 19, 2022, at 9:55 AM, John Maddock via Boost <boost@lists.boost.org> 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. Go ahead. — Marshall
On 05/04/2022 18:06, Marshall Clow via Boost wrote:
On Mar 19, 2022, at 9:55 AM, John Maddock via Boost <boost@lists.boost.org> 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
The master branch is is now open for post-beta merges, but only as described in the Post-Beta Merge Policy.
pdimov made a really cool little travis action to easily see if master is behind develop on a set of repos I adapted it for GitHub Actions (just for my repos and CMT repos): https://github.com/jeking3/boost-merge-reminder/actions/runs/2016167548 Scanned what got missed to see if it's just CI work or not: assign: a change to remove the dependency on MPL date_time: a Y2K38 bugfix pool: fix integer overflows in pool::ordered_malloc (github #42; trac #6701) property_map: compiler warnings, fix previous attempt to hide dependency on _parallel (root cause of some clean build issues) ptr_container: doc changes (invalid XHTML fixes) concept_check: just CI work; no changes since 1.76 dynamic_bitset: just CI work; no changes since 1.76 logic: mostly CI work; test-only changes (switched to lightweight test); no code changes since 1.76 Thanks, Jim
śr., 16 mar 2022 o 18:13 Marshall Clow via Boost <boost@lists.boost.org> napisał(a):
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/>
— Marshall
P.S Doc changes and test changes do NOT require release manager approval to be merged.
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
I request permission to merge the develop branch to master for Optional. The commits that affect the library sources (as opposed to only test and docs changes and external build system configuration (Optional is a header only library)) are: * c300a8c <https://github.com/boostorg/optional/commit/c300a8c517869d549a13a6dbd9943218a42df7f6> Change aligned_storage::dummy::data to unsigned char[] * 4f713ac <https://github.com/boostorg/optional/commit/4f713acdf875e1d7fc118b349158e4a09ec62ae9> Construct the unqualified value_type with placement new * 7dd512a <https://github.com/boostorg/optional/commit/7dd512a0196205f45a481bbbc302f8bf4d92626e> Fix issue #98 <https://github.com/boostorg/optional/issues/98> * d0ab800 <https://github.com/boostorg/optional/commit/d0ab8004c016dc71366f6624856595713df061ae> Add support for BOOST_NO_IOSTREAM They are all bug fixes, and have been under test in branch `develop` since Mar 1. My apologies for requesting it so late. Regards, &rzej;
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.
On Apr 6, 2022, at 12:56 PM, Andrey Semashev via Boost <boost@lists.boost.org> 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
participants (7)
-
Andrey Semashev -
Andrzej Krzemienski -
James E. King III -
John Maddock -
Marshall Clow -
Niall Douglas -
René Ferdinand Rivera Morell