[release] 1.76.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/boost/wiki/Releases%3A-Beta-Merge-Policy> Reminder: The master branch closes for the release on Wednesday, Apr 7. 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 3/16/21 11:24 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/boost/wiki/Releases%3A-Beta-Merge-Policy>
Reminder: The master branch closes for the release on Wednesday, Apr 7. Full calendar here: https://www.boost.org/development/ <https://www.boost.org/development/>
I would like to merge Boost.Parameter develop to master: https://github.com/boostorg/parameter/compare/master...develop The changes are: - Added cxxstd metadata (https://github.com/boostorg/parameter/pull/107) - Added a workaround for MSVC 2015 code miscompilation related to rvalue references (https://github.com/boostorg/parameter/pull/109) - Added readme file. - CI updates. - Minor test fixes (added a missing include and changed Boost.Bind include to silence deprecated warnings). CI tests have passed.
On 3/16/21 11:24 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/boost/wiki/Releases%3A-Beta-Merge-Policy> Reminder: The master branch closes for the release on Wednesday, Apr 7. Full calendar here: https://www.boost.org/development/ <https://www.boost.org/development/>
I would like to merge critical fixes implemented in Boost.Histogram develop to master: https://github.com/boostorg/histogram/compare/master...develop The change: `accumulators::mean` and `accumulators::weighted_mean` now compute the correct variance when `operator+=` is called, for example, when histograms with accumulators are added; this was wrong before leading to too small variances Unit tests were rewritten to catch this error and do have a more clear structure. Comments were added to code and some doxygen strings fixed. CI tests have passed. Best regards, Hans _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Go ahead.
On Mar 17, 2021, at 4:07 AM, Hans Dembinski via Boost <boost@lists.boost.org> wrote:
On 3/16/21 11:24 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/boost/wiki/Releases%3A-Beta-Merge-Policy> Reminder: The master branch closes for the release on Wednesday, Apr 7. Full calendar here: https://www.boost.org/development/ <https://www.boost.org/development/>
I would like to merge critical fixes implemented in Boost.Histogram develop to master:
https://github.com/boostorg/histogram/compare/master...develop
The change:
`accumulators::mean` and `accumulators::weighted_mean` now compute the correct variance when `operator+=` is called, for example, when histograms with accumulators are added; this was wrong before leading to too small variances
Unit tests were rewritten to catch this error and do have a more clear structure. Comments were added to code and some doxygen strings fixed. CI tests have passed.
Best regards, Hans _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Go ahead.
On Mar 17, 2021, at 3:46 AM, Andrey Semashev via Boost <boost@lists.boost.org> wrote:
On 3/16/21 11:24 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/boost/wiki/Releases%3A-Beta-Merge-Policy> Reminder: The master branch closes for the release on Wednesday, Apr 7. Full calendar here: https://www.boost.org/development/ <https://www.boost.org/development/>
I would like to merge Boost.Parameter develop to master:
https://github.com/boostorg/parameter/compare/master...develop
The changes are:
- Added cxxstd metadata (https://github.com/boostorg/parameter/pull/107) - Added a workaround for MSVC 2015 code miscompilation related to rvalue references (https://github.com/boostorg/parameter/pull/109) - Added readme file. - CI updates. - Minor test fixes (added a missing include and changed Boost.Bind include to silence deprecated warnings).
CI tests have passed.
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
On 3/16/21 11:24 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/boost/wiki/Releases%3A-Beta-Merge-Policy>
Reminder: The master branch closes for the release on Wednesday, Apr 7. Full calendar here: https://www.boost.org/development/ <https://www.boost.org/development/>
I would like to merge the following fix to Boost.Detail master: https://github.com/boostorg/detail/commit/131208d8ccd82ef69afb9cf0bad1a314bd... Fixes a potential out-of-bounds access in utf8_codecvt_facet::do_length. CI tests have passed.
Go ahead.
On Mar 17, 2021, at 5:02 AM, Andrey Semashev via Boost <boost@lists.boost.org> wrote:
On 3/16/21 11:24 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/boost/wiki/Releases%3A-Beta-Merge-Policy> Reminder: The master branch closes for the release on Wednesday, Apr 7. Full calendar here: https://www.boost.org/development/ <https://www.boost.org/development/>
I would like to merge the following fix to Boost.Detail master:
https://github.com/boostorg/detail/commit/131208d8ccd82ef69afb9cf0bad1a314bd...
Fixes a potential out-of-bounds access in utf8_codecvt_facet::do_length.
CI tests have passed.
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
On Tue, 16 Mar 2021 at 21:25, 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/boost/wiki/Releases%3A-Beta-Merge-Policy>
Reminder: The master branch closes for the release on Wednesday, Apr 7. 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.
Pleas be advised. property_tree fixes and CI merged to master. PR pending on the website repo with corresponding release notes.
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
-- Richard Hodges hodges.r@gmail.com office: +44 2032 898 513 home: +376 861 195 mobile: +376 380 212
P.S Doc changes and test changes do NOT require release manager approval to be merged.
I have merged the latest beast develop onto master to capture some CI/testing updates. One of the commits in there is a bugfix for MSVC for which I understand I should have sought approval first. My apologies for the inadvertent break in protocol. R
I've had a request to merge these new Boost.Config feature checks to release as Serialization depends on them: https://github.com/boostorg/config/pull/369 Technically it's a new feature and should be out of the scope of merging at this time, but as it effects nothing else I hope it should be low risk. Also related to Serialization, this bugfix for BOOST_HAS_HASH should probably go in: https://github.com/boostorg/config/pull/374. Note that these only impact the serialization *tests*, library user experience is unaffected. So we could probably live with this as it is and not merge at this time if needs be. Thanks, John. -- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus
On Tue, Mar 16, 2021 at 1:25 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/boost/wiki/Releases%3A-Beta-Merge-Policy>
I'd like to merge Boost.JSON develop to master which contains Necessary Fixes from Very Reliable Sources <https://github.com/boostorg/json/commits/develop> <https://github.com/boostorg/json/commits/master> Thanks
On 16. Mar 2021, at 21:24, 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/boost/wiki/Releases%3A-Beta-Merge-Policy>
Reminder: The master branch closes for the release on Wednesday, Apr 7. Full calendar here: https://www.boost.org/development/ <https://www.boost.org/development/>
I would like to again merge Boost.Histogram develop to master: https://github.com/boostorg/histogram/compare/master...develop Apart from Peter's whitespace change this includes the following bug-fix: - detection of weight support in user-defined accumulators was broken at compile-time if accumulator used `operator+=` instead of `operator()` Best regards, Hans
On 16/03/2021 20:24, 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/boost/wiki/Releases%3A-Beta-Merge-Policy>
I would like to fix https://github.com/ned14/outcome/issues/249 by improving the logic at https://github.com/ned14/outcome/blob/develop/include/outcome/convert.hpp#L3... please. Niall
On Mar 25, 2021, at 8:06 AM, Niall Douglas via Boost <boost@lists.boost.org> wrote:
On 16/03/2021 20:24, 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/boost/wiki/Releases%3A-Beta-Merge-Policy>
I would like to fix https://github.com/ned14/outcome/issues/249 by improving the logic at https://github.com/ned14/outcome/blob/develop/include/outcome/convert.hpp#L3... please.
Do you have a commit that fixes this? — Marshall
On 25/03/2021 15:45, Marshall Clow wrote:
On Mar 25, 2021, at 8:06 AM, Niall Douglas via Boost <boost@lists.boost.org> wrote:
On 16/03/2021 20:24, 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/boost/wiki/Releases%3A-Beta-Merge-Policy>
I would like to fix https://github.com/ned14/outcome/issues/249 by improving the logic at https://github.com/ned14/outcome/blob/develop/include/outcome/convert.hpp#L3... please.
Do you have a commit that fixes this?
The change is trivial. Current: ```c++ #if !defined(_MSC_VER) && !defined(__clang__) && (__GNUC__ < 9 || __cpp_concepts < 201907L) #define OUTCOME_GCC6_CONCEPT_BOOL bool #else #define OUTCOME_GCC6_CONCEPT_BOOL #endif ``` To be replaced with: ```c++ #if (defined(_MSC_VER) || defined(__clang__) || (defined(__GNUC__) && __cpp_concepts >= 201707) || OUTCOME_FORCE_STD_CXX_CONCEPTS) && !OUTCOME_FORCE_LEGACY_GCC_CXX_CONCEPTS #define OUTCOME_GCC6_CONCEPT_BOOL #else #define OUTCOME_GCC6_CONCEPT_BOOL bool #endif ``` To explain, GCC expects bool with concept, or not, in varying configuration combinations which have evolved over GCC versions, including apparently point releases, which is deeply unhelpful. This has led to repeated bug reports for not just Outcome, but also for ASIO and many other C++ projects. If this above fix doesn't permanently shut this constant source of bug reports, I'll be permanently disabling legacy GCC concepts support in Outcome. I couldn't be arsed with supporting how unpredictably broken GCC is with this. Niall
On Thu, Mar 25, 2021 at 12:04 PM Niall Douglas via Boost <boost@lists.boost.org> wrote:
On 25/03/2021 15:45, Marshall Clow wrote:
On Mar 25, 2021, at 8:06 AM, Niall Douglas via Boost <boost@lists.boost.org> wrote:
I would like to fix https://github.com/ned14/outcome/issues/249 by improving the logic at https://github.com/ned14/outcome/blob/develop/include/outcome/convert.hpp#L3... please.
Do you have a commit that fixes this?
The change is trivial. Current:
If you're asking for permission to merge to master now, you should have a commit on outcome's develop branch that we can look at. You are free to commit to develop at any time. Only master is locked. Glen
On 25/03/2021 15:45, Marshall Clow wrote:
On Mar 25, 2021, at 8:06 AM, Niall Douglas via Boost <boost@lists.boost.org> wrote:
On 16/03/2021 20:24, 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/boost/wiki/Releases%3A-Beta-Merge-Policy>
I would like to fix https://github.com/ned14/outcome/issues/249 by improving the logic at https://github.com/ned14/outcome/blob/develop/include/outcome/convert.hpp#L3... please.
Do you have a commit that fixes this?
Judging from https://www.boost.org/development/tests/develop/developer/outcome.html, the commit fixing this shown at https://github.com/boostorg/outcome/commits/develop has not broken anything. May I merge this to master? Niall
On Mon, Mar 29, 2021 at 6:43 AM Niall Douglas via Boost <boost@lists.boost.org> wrote:
Judging from https://www.boost.org/development/tests/develop/developer/outcome.html, the commit fixing this shown at https://github.com/boostorg/outcome/commits/develop has not broken anything.
May I merge this to master?
Go ahead. Glen
I would like to merge the following commits to master: Fix case where inflated content is larger than out buffer https://github.com/boostorg/beast/pull/2207/commits/8283a7df3faf555f3697aa2a... minor tweak to github actions workflow: https://github.com/boostorg/beast/pull/2207/commits/26e9a4c2947c1870f511c607... Fix missing check for error code after header is parsed https://github.com/boostorg/beast/pull/2207/commits/31a1fb332a8f69ae35853216... Correct an incorrect test https://github.com/boostorg/beast/pull/2207/commits/c3e83439dd7c3590a00ff873... Update version number https://github.com/boostorg/beast/pull/2207/commits/b7344b0d501f23f763a76488... On Tue, 16 Mar 2021 at 21:25, 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/boost/wiki/Releases%3A-Beta-Merge-Policy>
Reminder: The master branch closes for the release on Wednesday, Apr 7. 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
On 3/16/21 11:24 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/boost/wiki/Releases%3A-Beta-Merge-Policy>
Reminder: The master branch closes for the release on Wednesday, Apr 7. Full calendar here: https://www.boost.org/development/ <https://www.boost.org/development/>
I'd like to merge the following commit to Boost.Filesystem master: https://github.com/boostorg/filesystem/commit/83429c9bfd9c305fa35dbf15bbcd12... This is a fix for create_directories returning a wrong error_code if an internal file status query fails. CI tests passed.
On Mon, Mar 29, 2021 at 5:23 PM Andrey Semashev via Boost <boost@lists.boost.org> wrote:
I'd like to merge the following commit to Boost.Filesystem master:
https://github.com/boostorg/filesystem/commit/83429c9bfd9c305fa35dbf15bbcd12...
This is a fix for create_directories returning a wrong error_code if an internal file status query fails.
Go ahead Glen
On Tue, Mar 16, 2021 at 3:25 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/boost/wiki/Releases%3A-Beta-Merge-Policy>
I'd like to merge the latest B2 4.5.0 release to master. Only minor fixes for python and Windows bootstrap/build < https://github.com/bfgroup/b2/releases/tag/4.5.0>. -- -- René Ferdinand Rivera Morell -- Don't Assume Anything -- No Supone Nada -- Robot Dreams - http://robot-dreams.net
On Wed, Mar 31, 2021 at 9:20 AM René Ferdinand Rivera Morell < grafikrobot@gmail.com> wrote:
On Tue, Mar 16, 2021 at 3:25 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/boost/wiki/Releases%3A-Beta-Merge-Policy
I'd like to merge the latest B2 4.5.0 release to master. Only minor fixes for python and Windows bootstrap/build < https://github.com/bfgroup/b2/releases/tag/4.5.0>.
Any word on this? Can I merge? Other than documentation changes this includes a fix to the long standing problems with Python "m" suffixed build files/dirs/libs. -- -- René Ferdinand Rivera Morell -- Don't Assume Anything -- No Supone Nada -- Robot Dreams - http://robot-dreams.net
On 3/16/21 1:24 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/boost/wiki/Releases%3A-Beta-Merge-Policy>
Reminder: The master branch closes for the release on Wednesday, Apr 7. 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 would like to merge the latest changes of the serialization library into the release. This is so that things are syncronized with recently merged changes to config.hpp Robert Ramey
On 16/03/2021 20:24, 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/boost/wiki/Releases%3A-Beta-Merge-Policy>
I'd like to merge this change: https://github.com/boostorg/math/pull/593 to master if possible. Explanation: parallel execution of some algorithms has been newly added to this release, but we've found one (Gini coefficient calculation) to be faulty, this PR is a temporary sticking plaster that directs everything to the serial algorithm. The one CI failure is spurious (I haven't yet merged a CircleCI config to develop, much less master, but it is enabled for the repository while I work on getting that ready for develop). Many thanks, John. -- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus
On 01/04/2021 16:39, John Maddock wrote:
On 16/03/2021 20:24, 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/boost/wiki/Releases%3A-Beta-Merge-Policy>
I'd like to merge this change: https://github.com/boostorg/math/pull/593 to master if possible.
Explanation: parallel execution of some algorithms has been newly added to this release, but we've found one (Gini coefficient calculation) to be faulty, this PR is a temporary sticking plaster that directs everything to the serial algorithm.
The one CI failure is spurious (I haven't yet merged a CircleCI config to develop, much less master, but it is enabled for the repository while I work on getting that ready for develop).
Many thanks, John.
Ping? -- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus
On 3/16/21 11:24 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/boost/wiki/Releases%3A-Beta-Merge-Policy>
Reminder: The master branch closes for the release on Wednesday, Apr 7. Full calendar here: https://www.boost.org/development/ <https://www.boost.org/development/>
I'd like to merge the following PR to Boost.Atomic master: https://github.com/boostorg/atomic/pull/49 This fixes compilation with MSVC for ARM. CI tests have passed.
On Fri, Apr 2, 2021 at 6:40 AM Andrey Semashev via Boost <boost@lists.boost.org> wrote:
I'd like to merge the following PR to Boost.Atomic master:
https://github.com/boostorg/atomic/pull/49
This fixes compilation with MSVC for ARM.
CI tests have passed.
Go ahead and merge. Glen
On 3/16/21 11:24 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/boost/wiki/Releases%3A-Beta-Merge-Policy>
Reminder: The master branch closes for the release on Wednesday, Apr 7. Full calendar here: https://www.boost.org/development/ <https://www.boost.org/development/>
I would like to merge the following PR to Boost.Log master: https://github.com/boostorg/log/pull/149 It fixes incompatibility with MinGW-w64 when building against UCRT.
I would like to merge the following PR to Boost.Log master:
https://github.com/boostorg/log/pull/149
It fixes incompatibility with MinGW-w64 when building against UCRT.
And I'd like to merge basically the same fix for Nowide: https://github.com/boostorg/nowide/pull/130
On Tue, 16 Mar 2021 at 21:25, 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/boost/wiki/Releases%3A-Beta-Merge-Policy>
Reminder: The master branch closes for the release on Wednesday, Apr 7. Full calendar here: https://www.boost.org/development/ < https://www.boost.org/development/>
I'll need to make one commit later on today. This will be limited to correcting an incorrect assumption in one test and only affects the reliability of the green build indicator. I think it's important to squeeze this one in as otherwise we might undermine confidence in the library after the release. Sorry for the late notice.
On Tue, 6 Apr 2021 at 15:53, Richard Hodges <hodges.r@gmail.com> wrote:
On Tue, 16 Mar 2021 at 21:25, 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/boost/wiki/Releases%3A-Beta-Merge-Policy
Reminder: The master branch closes for the release on Wednesday, Apr 7. Full calendar here: https://www.boost.org/development/ < https://www.boost.org/development/>
I'll need to make one commit later on today. This will be limited to correcting an incorrect assumption in one test and only affects the reliability of the green build indicator.
I think it's important to squeeze this one in as otherwise we might undermine confidence in the library after the release.
Sorry for the late notice.
Once again I feel obliged to apologise to the release managers. I inadvertently rebased my changes onto master rather than develop before seeking approval for updating beast master. No production code is affected. Commit details are here: Fix a test to make it deterministic https://github.com/boostorg/beast/commit/7257d64a2179621d5514a310472ad28db49... Compensate for the upstream removal of older compilers in the ubuntu GHA image https://github.com/boostorg/beast/commit/fa1004fcbfaa9c8b654115438aa7efc9d76... Set version number https://github.com/boostorg/beast/commit/83aaefaf725d2dd125132c40a3f26811979...
Hello Marshall, On 16.03.21 21:24, 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/boost/wiki/Releases%3A-Beta-Merge-Policy>
Reminder: The master branch closes for the release on Wednesday, Apr 7. Full calendar here: https://www.boost.org/development/ <https://www.boost.org/development/>
Could you please bring the MSVC fix for concept_check to master so that is is included in 1.76? https://github.com/boostorg/concept_check/issues/31 Thanks, Gregor
participants (12)
-
Alexander Grund -
Andrey Semashev -
Glen Fernandes -
Gregor Jasny -
Hans Dembinski -
John Maddock -
Marshall Clow -
Niall Douglas -
René Ferdinand Rivera Morell -
Richard Hodges -
Robert Ramey -
Vinnie Falco