[boost] [release] Boost 1.79.0

54 views
Skip to first unread message

Marshall Clow via Boost

unread,
Apr 13, 2022, 11:13:32 AM4/13/22
to Boost Developers List, Boost users list, boost-a...@lists.boost.org, Marshall Clow
Release 1.79.0 of the Boost C++ Libraries is now available.

These open-source libraries work well with the C++ Standard Library, and are usable across a broad spectrum of applications. The Boost license encourages both commercial and non-commercial use.

This release contains numerous enhancements and bug fixes for existing libraries.

For details, including download links, see <http://www.boost.org/users/news/version_1.79.0>

You can also download directly from: <https://boostorg.jfrog.io/artifactory/main/release/1.79.0/>

To install this release on your system, see <http://www.boost.org/doc/libs/release/more/getting_started/index.html>

Thanks to everyone who participated in this release.

-- The Boost Release Team

Marshall Clow, Michael Caisse, Glen Fernandes

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

Vinnie Falco via Boost

unread,
Apr 13, 2022, 2:04:55 PM4/13/22
to Boost users list, Vinnie Falco, Boost Developers List
On Wed, Apr 13, 2022 at 8:13 AM Marshall Clow via Boost-users
<boost...@lists.boost.org> 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>

Thanks

Niall Douglas via Boost

unread,
Apr 13, 2022, 2:27:31 PM4/13/22
to bo...@lists.boost.org, Niall Douglas
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.

Niall

boost_outcome_hotfix.diff

Andrey Semashev via Boost

unread,
Apr 13, 2022, 3:17:34 PM4/13/22
to bo...@lists.boost.org, Andrey Semashev
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
> <boost...@lists.boost.org> 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.

Andrey Semashev via Boost

unread,
Apr 13, 2022, 3:20:27 PM4/13/22
to bo...@lists.boost.org, Andrey Semashev
Patches are better attached to release notes.

😉 Good Guy 😉 via Boost

unread,
Apr 13, 2022, 3:27:18 PM4/13/22
to bo...@lists.boost.org, 😉 Good Guy 😉, boost...@lists.boost.org
On 13/04/2022 19:04, Vinnie Falco via Boost-users wrote:
> 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>
>

That's the beauty of modern technology especially the Internet which is
almost free relatively speaking for most people.

Niall Douglas via Boost

unread,
Apr 13, 2022, 5:50:19 PM4/13/22
to bo...@lists.boost.org, Niall Douglas
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

Vinnie Falco via Boost

unread,
Apr 13, 2022, 6:54:55 PM4/13/22
to boost@lists.boost.org List, Vinnie Falco
On Wed, Apr 13, 2022 at 12:20 PM Andrey Semashev via Boost
<bo...@lists.boost.org> wrote:
> Patches are better attached to release notes.

Sorry.. how exactly does this work?

Thanks

Glen Fernandes via Boost

unread,
Apr 13, 2022, 9:22:45 PM4/13/22
to bo...@lists.boost.org, Vinnie Falco, Andrey Semashev, boost...@lists.boost.org, Glen Fernandes
On Wed, Apr 13, 2022 at 3:17 PM Andrey Semashev wrote:
>
> On 4/13/22 21:04, Vinnie Falco via Boost wrote:
> > 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.

Updated:

https://github.com/boostorg/website/commit/0752dee32f149db385ea0f635886221b794e800d

Added /patches/1_79_0/0001-json-array-erase-relocate.patch and release
notes updated.

Glen

Andrey Semashev via Boost

unread,
Apr 14, 2022, 4:05:28 AM4/14/22
to bo...@lists.boost.org, Andrey Semashev
On 4/14/22 01:54, Vinnie Falco via Boost wrote:
> On Wed, Apr 13, 2022 at 12:20 PM Andrey Semashev via Boost
> <bo...@lists.boost.org> 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.qbk
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).

Kenneth Porter via Boost

unread,
Apr 14, 2022, 10:32:23 PM4/14/22
to bo...@lists.boost.org, Kenneth Porter
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

Robert Ramey via Boost

unread,
Apr 15, 2022, 4:51:12 PM4/15/22
to bo...@lists.boost.org, Robert Ramey
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?

Kenneth Porter via Boost

unread,
Apr 15, 2022, 8:11:52 PM4/15/22
to bo...@lists.boost.org, Kenneth Porter
On 4/15/2022 1:50 PM, Robert Ramey via Boost wrote:
> Hmmm - is there any reason you can't build it yourself locally?

I DO build it locally from the source zip file. And get those warnings.
So I have to re-apply those patches with every release.

Glen Fernandes via Boost

unread,
Apr 15, 2022, 9:34:10 PM4/15/22
to bo...@lists.boost.org, Glen Fernandes, Kenneth Porter
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

André Brand via Boost

unread,
Apr 24, 2022, 10:48:47 AM4/24/22
to bo...@lists.boost.org, André Brand

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?

André

Glen Fernandes via Boost

unread,
Apr 24, 2022, 10:50:47 AM4/24/22
to bo...@lists.boost.org, Glen Fernandes
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

Niall Douglas via Boost

unread,
Apr 26, 2022, 11:19:44 AM4/26/22
to bo...@lists.boost.org, Niall Douglas
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.
>
> 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).

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

I've had a few complaints since the 1.79 release about the breakage, all
to date have been happy with the patch or using current master branch.

Niall

Glen Fernandes via Boost

unread,
Apr 26, 2022, 12:10:45 PM4/26/22
to bo...@lists.boost.org, Glen Fernandes
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

Reply all
Reply to author
Forward
0 new messages