On 4/13/22 21:04, Vinnie Falco via Boost wrote:

On Wed, Apr 13, 2022 at 8:13 AM Marshall Clow via Boost-users wrote:

...

Release 1.79.0 of the Boost C++ Libraries is now available.

The thing that I absolutely LOVE about a new release of Boost, is that someone always reports a crashing bug just after the release is published:

https://github.com/boostorg/json/issues/692

We have a practice of adding post-release patches to release notes.

On 13/04/2022 20:20, Andrey Semashev via Boost wrote:

On 4/13/22 21:27, Niall Douglas via Boost wrote:

...

On 13/04/2022 16:12, Marshall Clow via Boost wrote:

...

Release 1.79.0 of the Boost C++ Libraries is now available.

Hotfix for Outcome for this release is attached, as promised.

Patches are better attached to release notes.

Release note is this: Fix support for assignment of non-move non-copy constructible types when void is the alternate. Niall

On 4/14/22 01:54, Vinnie Falco via Boost wrote:

On Wed, Apr 13, 2022 at 12:20 PM Andrey Semashev via Boost wrote:

...

Patches are better attached to release notes.

Sorry.. how exactly does this work?

You create a PR for the website. Add a note in https://github.com/boostorg/website/blob/master/feed/history/boost_1_79_0.qb... with a link to the patch that applies to the release package. You put the patch in https://github.com/boostorg/website/tree/master/patches. It looks like Glen Fernandes already did it for you (thanks, Glen).

On Sun, Apr 24, 2022 at 10:48 AM André Brand wrote:

On 13/04/2022 20:27, Niall Douglas via Boost wrote:

...

Hotfix for Outcome for this release is attached, as promised.

The patch is still not listed in the release notes on the boost website; only the patch for Boost.JSON is.

Is this still regarded as an unofficial patch for some reason?

It only becomes official once it's on the Boost website. Niall has to submit a pull request to boostorg/website with a patch relative to the Boost release distribution (not the Github repository, because the layout is different). Glen

On Tue, Apr 26, 2022 at 11:19 AM Niall Douglas wrote:

On 24/04/2022 15:50, Glen Fernandes via Boost wrote:

...

On Sun, Apr 24, 2022 at 10:48 AM André Brand wrote:

...

On 13/04/2022 20:27, Niall Douglas via Boost wrote:

...

Hotfix for Outcome for this release is attached, as promised.

The patch is still not listed in the release notes on the boost website; only the patch for Boost.JSON is.

Is this still regarded as an unofficial patch for some reason?

It only becomes official once it's on the Boost website.

The patch was good enough for those who needed it e.g. package distributors, which was all that was needed from my perspective.

i.e. To answer André's question: Yes, by design: You don't need an Outcome patch on the Boost website for 1.79.0. Glen

On 4/14/22 7:31 PM, Kenneth Porter via Boost wrote:

I like to get a clean build with no warnings (since they obscure real problems) and have submitted a couple of issues (different libraries) with patches but haven't seem them make it into the latest release. Do I need to make a PR? The patches are pretty simple. (The second issue here has 2 PRs.)

https://github.com/boostorg/locale/issues/42

https://github.com/boostorg/crc/issues/18

Hmmm - is there any reason you can't build it yourself locally?

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

On Thu, Apr 14, 2022 at 10:32 PM Kenneth Porter wrote:

I like to get a clean build with no warnings (since they obscure real problems) and have submitted a couple of issues (different libraries) with patches but haven't seem them make it into the latest release.

I'll address the CRC ones for 1.80.0. Glen