[boost] [release] Boost 1.80.0 Release Candidate 1 is available

[Marshall Clow via Boost]

The first release candidates for the 1.80.0 release are now available at:
<https://boostorg.jfrog.io/artifactory/main/release/1.80.0/source/>

The SHA256 checksums are as follows:

4b2136f98bdd1f5857f1c3dea9ac2018effe65286cf251534b6ae20cc45e1847 boost_1_80_0_rc1.tar.gz
1e19565d82e43bc59209a168f5ac899d3ba471d55c7610c677d4ccf2c9c500c0 boost_1_80_0_rc1.tar.bz2
d12a2af721e22dbfb984ef061ee4c4ab2387f1904f6d65bc5acebaa34d6366ec boost_1_80_0_rc1.7z
e34756f63abe8ac34b35352743f17d061fcc825969a2dd8458264edb38781782 boost_1_80_0_rc1.zip


As always, the release managers would appreciate it if you download the
candidate of your choice and give building it a try. Please report both
success and failure, and anything else that is noteworthy.

-- The Release managers

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

[Marshall Clow via Boost]

On Aug 4, 2022, at 6:25 AM, Marshall Clow <mclow...@gmail.com> wrote:
>
> The first release candidates for the 1.80.0 release are now available at:
> <https://boostorg.jfrog.io/artifactory/main/release/1.80.0/source/>
>
> The SHA256 checksums are as follows:
>
> 4b2136f98bdd1f5857f1c3dea9ac2018effe65286cf251534b6ae20cc45e1847 boost_1_80_0_rc1.tar.gz
> 1e19565d82e43bc59209a168f5ac899d3ba471d55c7610c677d4ccf2c9c500c0 boost_1_80_0_rc1.tar.bz2
> d12a2af721e22dbfb984ef061ee4c4ab2387f1904f6d65bc5acebaa34d6366ec boost_1_80_0_rc1.7z
> e34756f63abe8ac34b35352743f17d061fcc825969a2dd8458264edb38781782 boost_1_80_0_rc1.zip
>
>
> As always, the release managers would appreciate it if you download the
> candidate of your choice and give building it a try. Please report both
> success and failure, and anything else that is noteworthy.

I have successfully built the libraries on Mac OS 10.15.7, using
Apple clang version 11.0.3 (clang-1103.0.32.62) and c++03/11/14/17/2a

— Marshall

[Tom Kent via Boost]

On Thu, Aug 4, 2022 at 8:25 AM Marshall Clow via Boost <
bo...@lists.boost.org> wrote:

> The first release candidates for the 1.80.0 release are now available at:
> <https://boostorg.jfrog.io/artifactory/main/release/1.80.0/source/>
>
> The SHA256 checksums are as follows:
>
> 4b2136f98bdd1f5857f1c3dea9ac2018effe65286cf251534b6ae20cc45e1847
> boost_1_80_0_rc1.tar.gz
> 1e19565d82e43bc59209a168f5ac899d3ba471d55c7610c677d4ccf2c9c500c0
> boost_1_80_0_rc1.tar.bz2
> d12a2af721e22dbfb984ef061ee4c4ab2387f1904f6d65bc5acebaa34d6366ec
> boost_1_80_0_rc1.7z
> e34756f63abe8ac34b35352743f17d061fcc825969a2dd8458264edb38781782
> boost_1_80_0_rc1.zip
>
>
> As always, the release managers would appreciate it if you download the
> candidate of your choice and give building it a try. Please report both
> success and failure, and anything else that is noteworthy.
>

Looks good on Windows/Visual Studio.

toolset arch compile Link Execute
msvc-10.0 32 X X X
msvc-10.0 64 X X X
msvc-11.0 32 X X X
msvc-11.0 64 X X X
msvc-12.0 32 X X X
msvc-12.0 64 X X X
msvc-14.0 32 X X X
msvc-14.0 64 X X X
msvc-14.1 32 X X X
msvc-14.1 64 X X X
msvc-14.2 32 X X X
msvc-14.2 64 X X X
msvc-14.3 32 X X X
msvc-14.3 64 X X X

Compile means that the b2 command completed without errors
Link means that visual studio was able to link a sample executable to a
library (libboost_thread-vcXXX-mt[-gd]-1_XX.lib) generated
Execute means that the linked program executed without errors.

Full build logs can be found here:
https://gist.github.com/teeks99/6b678c9fbf78e77bf8342c29496fae9d

Tom

[Andrey Semashev via Boost]

On 8/4/22 16:25, Marshall Clow via Boost wrote:
> The first release candidates for the 1.80.0 release are now available at:
> <https://boostorg.jfrog.io/artifactory/main/release/1.80.0/source/>
>
> The SHA256 checksums are as follows:
>
> 4b2136f98bdd1f5857f1c3dea9ac2018effe65286cf251534b6ae20cc45e1847 boost_1_80_0_rc1.tar.gz
> 1e19565d82e43bc59209a168f5ac899d3ba471d55c7610c677d4ccf2c9c500c0 boost_1_80_0_rc1.tar.bz2
> d12a2af721e22dbfb984ef061ee4c4ab2387f1904f6d65bc5acebaa34d6366ec boost_1_80_0_rc1.7z
> e34756f63abe8ac34b35352743f17d061fcc825969a2dd8458264edb38781782 boost_1_80_0_rc1.zip
>
>
> As always, the release managers would appreciate it if you download the
> candidate of your choice and give building it a try. Please report both
> success and failure, and anything else that is noteworthy.

I would like to merge this last minute fix to Boost.Filesystem master:

https://github.com/boostorg/filesystem/commit/9c9d127bddc2b72187c57f4933c49666255d7a4f

This should fix error constructing a directory iterator over a network
share on Windows prior to 10.

[Marshall Clow via Boost]

On Aug 8, 2022, at 7:25 AM, Andrey Semashev via Boost <bo...@lists.boost.org> wrote:
>
> On 8/4/22 16:25, Marshall Clow via Boost wrote:
>> The first release candidates for the 1.80.0 release are now available at:
>> <https://boostorg.jfrog.io/artifactory/main/release/1.80.0/source/>
>>
>> The SHA256 checksums are as follows:
>>
>> 4b2136f98bdd1f5857f1c3dea9ac2018effe65286cf251534b6ae20cc45e1847 boost_1_80_0_rc1.tar.gz
>> 1e19565d82e43bc59209a168f5ac899d3ba471d55c7610c677d4ccf2c9c500c0 boost_1_80_0_rc1.tar.bz2
>> d12a2af721e22dbfb984ef061ee4c4ab2387f1904f6d65bc5acebaa34d6366ec boost_1_80_0_rc1.7z
>> e34756f63abe8ac34b35352743f17d061fcc825969a2dd8458264edb38781782 boost_1_80_0_rc1.zip
>>
>>
>> As always, the release managers would appreciate it if you download the
>> candidate of your choice and give building it a try. Please report both
>> success and failure, and anything else that is noteworthy.
>
> I would like to merge this last minute fix to Boost.Filesystem master:
>
> https://github.com/boostorg/filesystem/commit/9c9d127bddc2b72187c57f4933c49666255d7a4f
>
> This should fix error constructing a directory iterator over a network
> share on Windows prior to 10.

Is this a regression against 1.79.0?

— Marshall

[Andrey Semashev via Boost]

On 8/9/22 01:27, Marshall Clow via Boost wrote:
> On Aug 8, 2022, at 7:25 AM, Andrey Semashev via Boost <bo...@lists.boost.org> wrote:
>>
>> On 8/4/22 16:25, Marshall Clow via Boost wrote:
>>> The first release candidates for the 1.80.0 release are now available at:
>>> <https://boostorg.jfrog.io/artifactory/main/release/1.80.0/source/>
>>>
>>> The SHA256 checksums are as follows:
>>>
>>> 4b2136f98bdd1f5857f1c3dea9ac2018effe65286cf251534b6ae20cc45e1847 boost_1_80_0_rc1.tar.gz
>>> 1e19565d82e43bc59209a168f5ac899d3ba471d55c7610c677d4ccf2c9c500c0 boost_1_80_0_rc1.tar.bz2
>>> d12a2af721e22dbfb984ef061ee4c4ab2387f1904f6d65bc5acebaa34d6366ec boost_1_80_0_rc1.7z
>>> e34756f63abe8ac34b35352743f17d061fcc825969a2dd8458264edb38781782 boost_1_80_0_rc1.zip
>>>
>>>
>>> As always, the release managers would appreciate it if you download the
>>> candidate of your choice and give building it a try. Please report both
>>> success and failure, and anything else that is noteworthy.
>>
>> I would like to merge this last minute fix to Boost.Filesystem master:
>>
>> https://github.com/boostorg/filesystem/commit/9c9d127bddc2b72187c57f4933c49666255d7a4f
>>
>> This should fix error constructing a directory iterator over a network
>> share on Windows prior to 10.
>
> Is this a regression against 1.79.0?

The problem was introduced in 1.79.0, so a regression since 1.78.0.

[Andrey Semashev via Boost]

Gentle ping. 1.80 release is closing in, so if we're going to allow this
change in, please let me know ASAP.

[Marshall Clow via Boost]

I talked to the other release managers, and we’re thinking .. not.

The reasons are:
* This has been this way since April, and no one noticed until last week.
* Your checkin comment does not exactly fill me with confidence: “probably fixes #246”
* Windows 10 was released in 2015.

This just doesn’t seem like a sufficient reason to roll an RC2.

— Marshall

[Andrey Semashev via Boost]

On 8/9/22 20:30, Marshall Clow wrote:
> On Aug 9, 2022, at 10:17 AM, Andrey Semashev via Boost

> <bo...@lists.boost.org <mailto:bo...@lists.boost.org>> wrote:
>>
>> On 8/9/22 02:48, Andrey Semashev wrote:
>>> On 8/9/22 01:27, Marshall Clow via Boost wrote:
>>>> On Aug 8, 2022, at 7:25 AM, Andrey Semashev via Boost

Ok.

Re. "Likely fixes" comment, I wrote that because I cannot test it myself
and one of the original reporters haven't responded (yet). The other
person who suggested the patch also had this problem and fixed it with
the patch, so I'm reasonably confident in it.

Alas, it seems to be the tradition now for multiple problem reports to
arrive during the release cycle.

[Marshall Clow via Boost]

It does.
And we (the release managers) discuss each one, and decide if it (or “they”, in aggregate) are serious enough to roll another release candidate.

This involves work for the release managers, but not *that* much. However, all the people who test the RCs then re-run their tests as well.

— Marshall