On 19/11/2018 18:43, Marshall Clow via Boost wrote:

On Sun, Nov 18, 2018 at 8:07 PM Robert Ramey via Boost < boost@lists.boost.org> wrote:

...

On 11/18/18 6:31 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/Release-Beta-Merge-Policy>

The master branch will close for the 1.69.0 release on 5-December. The release calendar is at https://www.boost.org/development/index.html

-- The Boost release team.

A heads up that I would like to merge the last round of changes to Boost.Math: there is one minor bug fix, plus a bunch of changes to the tests and CI scripts to try to eliminate spurious errors (timeouts etc).  See https://github.com/boostorg/math/compare/master...develop Thanks, John. --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus

On Sun, Nov 18, 2018 at 8:59 PM Rene Rivera via Boost wrote:

On Sun, Nov 18, 2018 at 8:32 PM Marshall Clow via Boost < boost@lists.boost.org> wrote:

...

The master branch is is now open for post-beta merges

There are a variety of b2 changes in develop that I'd like to merge to master. And there is a change in boost super-project that goes along with them. The changes amount to this:

* Make clang-win work. * Restore b2 documentation in release archive.

Can I merge the b2 develop state over to master? And would a PR for the boost super-project to generate tool documentation on master be acceptable?

Yes, and yes it would. http://lists.boost.org/mailman/listinfo.cgi/boost -- Marshall

On Mon, Nov 19, 2018 at 1:21 PM Rene Rivera wrote:

On Mon, Nov 19, 2018 at 12:43 PM Marshall Clow wrote:

...

On Sun, Nov 18, 2018 at 8:59 PM Rene Rivera via Boost < boost@lists.boost.org> wrote:

...

On Sun, Nov 18, 2018 at 8:32 PM Marshall Clow via Boost < boost@lists.boost.org> wrote:

...

The master branch is is now open for post-beta merges

There are a variety of b2 changes in develop that I'd like to merge to master. And there is a change in boost super-project that goes along with them. The changes amount to this:

* Make clang-win work. * Restore b2 documentation in release archive.

Can I merge the b2 develop state over to master? And would a PR for the boost super-project to generate tool documentation on master be acceptable?

Yes, and yes it would.

Done, and here's the PR https://github.com/boostorg/boost/pull/219

Could someone please merge that PR. Thanks in advance. -- -- Rene Rivera -- Grafik - Don't Assume Anything -- Robot Dreams - http://robot-dreams.net

On 20/11/2018 18:32, Ion Gaztañaga via Boost wrote:

On 19/11/2018 3:31, 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/Release-Beta-Merge-Policy>

The master branch will close for the 1.69.0 release on 5-December. The release calendar is at https://www.boost.org/development/index.html

I'd like to merge Boost.Container bugfixes, already cycled in develop:

#77 warning: 'sbrk' is deprecated #79 Mark small_vector move operations noexcept #81 Vector with custom allocator does not support value types with operator& #85 misc-typos #83 Iterator zero incrementing leads to assert on empty #84 Allow vector to be assigned to itself #86 Add missing warning re-enabling include #87 Fixed flat_map CTAD #89 Build fails on clang-5 with libstdc++7-dev #90 UBSAN failures detected in preflight CI PR

Kind ping. I'm also asking permission for some additional Interprocess commit I'd like to merge, specially Issue #64 Best, Ion

On Thu, Nov 22, 2018 at 2:17 PM Ion Gaztañaga via Boost < boost@lists.boost.org> wrote:

On 20/11/2018 18:32, Ion Gaztañaga via Boost wrote:

...

On 19/11/2018 3:31, 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/Release-Beta-Merge-Policy>

The master branch will close for the 1.69.0 release on 5-December. The release calendar is at https://www.boost.org/development/index.html

I'd like to merge Boost.Container bugfixes, already cycled in develop:

#77 warning: 'sbrk' is deprecated #79 Mark small_vector move operations noexcept #81 Vector with custom allocator does not support value types with operator& #85 misc-typos #83 Iterator zero incrementing leads to assert on empty #84 Allow vector to be assigned to itself #86 Add missing warning re-enabling include #87 Fixed flat_map CTAD #89 Build fails on clang-5 with libstdc++7-dev #90 UBSAN failures detected in preflight CI PR

Kind ping. I'm also asking permission for some additional Interprocess commit I'd like to merge, specially Issue #64

Approved. -- Marshall