[release] 1.71.0 closed for Beta
The master branch is now closed for all changes except by permission for the Beta release. Also, remember to add your libraries' changes to the release notes at: https://github.com/boostorg/website/blob/master/feed/history/boost_1_71_0.qb... Thanks, -- The Boost Release Team
On 12. Jul 2019, at 08:40, Michael Caisse via Boost
wrote: The master branch is now closed for all changes except by permission for the Beta release.
Also, remember to add your libraries' changes to the release notes at:
https://github.com/boostorg/website/blob/master/feed/history/boost_1_71_0.qb...
I ask for permission to merge two changes into the master: https://github.com/boostorg/histogram/commit/ac790609441da2d87f21023fdf9aeea... - fixes the axis::traits::update when the axis type is axis::variant https://github.com/boostorg/histogram/commit/2d8e83df6c26b4ff125010989ca6420... - update of the changelog (this I forgot to merge earlier, sorry) Best regards, Hans
On 7/12/19 01:07, Hans Dembinski wrote:
I ask for permission to merge two changes into the master:
https://github.com/boostorg/histogram/commit/ac790609441da2d87f21023fdf9aeea... - fixes the axis::traits::update when the axis type is axis::variant
https://github.com/boostorg/histogram/commit/2d8e83df6c26b4ff125010989ca6420... - update of the changelog (this I forgot to merge earlier, sorry)
Best regards, Hans
Please merge Hans. -- Michael Caisse Ciere Consulting ciere.com
On 7/12/19 9:40 AM, Michael Caisse via Boost wrote:
The master branch is now closed for all changes except by permission for the Beta release.
Also, remember to add your libraries' changes to the release notes at:
https://github.com/boostorg/website/blob/master/feed/history/boost_1_71_0.qb...
May I merge Boost.WinAPI to master? https://github.com/boostorg/winapi/commit/bb91190323166485a338b416446020a47b... Fixes compilation of Boost.Thread (and dependent libraries) with MSVC-12 on x86. https://github.com/boostorg/winapi/commit/f2789c82a4b16c9f6645fb10c0db6c62be... A test for the above. https://github.com/boostorg/winapi/commit/65b9c99a6772add56a24272d0b76b611fd... Fixes compilation of BOOST_INTERLOCKED_* macros on Cygwin64.
On 7/12/19 01:59, Andrey Semashev via Boost wrote:
May I merge Boost.WinAPI to master?
https://github.com/boostorg/winapi/commit/bb91190323166485a338b416446020a47b...
Fixes compilation of Boost.Thread (and dependent libraries) with MSVC-12 on x86.
https://github.com/boostorg/winapi/commit/f2789c82a4b16c9f6645fb10c0db6c62be...
A test for the above.
https://github.com/boostorg/winapi/commit/65b9c99a6772add56a24272d0b76b611fd...
Fixes compilation of BOOST_INTERLOCKED_* macros on Cygwin64.
Have the windows test runners cycled with this change? What is the breadth/variation of compilers/Windows OS versions that we have seen this cycle for? -- Michael Caisse Ciere Consulting ciere.com
On 7/12/19 7:15 PM, Michael Caisse via Boost wrote:
On 7/12/19 01:59, Andrey Semashev via Boost wrote:
May I merge Boost.WinAPI to master?
https://github.com/boostorg/winapi/commit/bb91190323166485a338b416446020a47b...
Fixes compilation of Boost.Thread (and dependent libraries) with MSVC-12 on x86.
https://github.com/boostorg/winapi/commit/f2789c82a4b16c9f6645fb10c0db6c62be...
A test for the above.
https://github.com/boostorg/winapi/commit/65b9c99a6772add56a24272d0b76b611fd...
Fixes compilation of BOOST_INTERLOCKED_* macros on Cygwin64.
Have the windows test runners cycled with this change?
Most of them did, including MSVC-12. We don't have official Cygwin runners. Appveyor CI for Boost.WinAPI has jobs for all MSVC and Cygwin and it passed all jobs: https://ci.appveyor.com/project/Lastique/winapi/builds/25875547
What is the breadth/variation of compilers/Windows OS versions that we have seen this cycle for?
Our official testers are limited to various MSVC versions: https://www.boost.org/development/tests/develop/developer/winapi.html Appveyor CI jobs are run on: - 32-bit x86: - MSVC-9, 10, 11, 12, 14.0, 14.1 - Cygwin - MinGW, MinGW-w64 (gcc 6.3.0) - 64-bit x86: - MSVC-12, 14.0, 14.1 - Cygwin64 - MinGW-w64 (gcc 7.3.0) I also ran the interlocked tests on MSVC-7.1 and 8 locally.
On 7/12/19 13:08, Andrey Semashev via Boost wrote:
On 7/12/19 7:15 PM, Michael Caisse via Boost wrote:
On 7/12/19 01:59, Andrey Semashev via Boost wrote:
May I merge Boost.WinAPI to master?
https://github.com/boostorg/winapi/commit/bb91190323166485a338b416446020a47b...
Fixes compilation of Boost.Thread (and dependent libraries) with MSVC-12 on x86.
https://github.com/boostorg/winapi/commit/f2789c82a4b16c9f6645fb10c0db6c62be...
A test for the above.
https://github.com/boostorg/winapi/commit/65b9c99a6772add56a24272d0b76b611fd...
Fixes compilation of BOOST_INTERLOCKED_* macros on Cygwin64.
Have the windows test runners cycled with this change?
Most of them did, including MSVC-12. We don't have official Cygwin runners. Appveyor CI for Boost.WinAPI has jobs for all MSVC and Cygwin and it passed all jobs:
https://ci.appveyor.com/project/Lastique/winapi/builds/25875547
What is the breadth/variation of compilers/Windows OS versions that we have seen this cycle for?
Our official testers are limited to various MSVC versions:
https://www.boost.org/development/tests/develop/developer/winapi.html
Appveyor CI jobs are run on:
- 32-bit x86: - MSVC-9, 10, 11, 12, 14.0, 14.1 - Cygwin - MinGW, MinGW-w64 (gcc 6.3.0)
- 64-bit x86: - MSVC-12, 14.0, 14.1 - Cygwin64 - MinGW-w64 (gcc 7.3.0)
I also ran the interlocked tests on MSVC-7.1 and 8 locally.
Thank you Andrey. Please merge the changes. -- Michael Caisse Ciere Consulting ciere.com
On Fri, Jul 12, 2019 at 2:40 AM Michael Caisse via Boost
The master branch is now closed for all changes except by permission for the Beta release.
Also, remember to add your libraries' changes to the release notes at:
https://github.com/boostorg/website/blob/master/feed/history/boost_1_71_0.qb...
Thanks,
-- The Boost Release Team
My apologies for not addressing these before the beta announcement, however there are a few changes not merged to master in two CMT maintained repositories: ptr_container: https://github.com/boostorg/ptr_container/commit/960da46f614fe526e0545614a98... Use unique temp file names to avoid spurious failures in parallel builds https://github.com/boostorg/ptr_container/pull/24 Fix a regression introduced at least as far back as 1.66.0 in ptr_vector There are also updates to the CI builds that pass on develop. logic: CI updates (added asan, tsan, VS2019, etc), no code changes. Thanks, Jim
I'm seeing the following block of warnings repeated with several MSVC compiler versions. I'd suggest changing int to ptrdiff_t or size_t for the target type. f:\devel\Boost\boost_1_71_0\libs\locale\src\win32\api.hpp(149): warning C4244: 'argument': conversion from '__int64' to 'int', possible loss of data f:\devel\Boost\boost_1_71_0\libs\locale\src\win32\api.hpp(153): warning C4267: 'argument': conversion from 'size_t' to 'int', possible loss of data f:\devel\Boost\boost_1_71_0\libs\locale\src\win32\api.hpp(153): warning C4244: 'argument': conversion from '__int64' to 'int', possible loss of data f:\devel\Boost\boost_1_71_0\libs\locale\src\win32\api.hpp(170): warning C4244: 'argument': conversion from '__int64' to 'int', possible loss of data f:\devel\Boost\boost_1_71_0\libs\locale\src\win32\api.hpp(245): warning C4244: 'argument': conversion from '__int64' to 'int', possible loss of data f:\devel\Boost\boost_1_71_0\libs\locale\src\win32\api.hpp(249): warning C4244: 'argument': conversion from '__int64' to 'int', possible loss of data My build command: call .\bootstrap.bat --without-python .\b2 --without-python toolset=msvc-14.2,msvc-14.0,msvc-12.0,msvc-10.0 runtime-link=shared,static address-model=32,64
participants (5)
-
Andrey Semashev
-
Hans Dembinski
-
James E. King III
-
Kenneth Porter
-
Michael Caisse