[release] Boost 1.89.0 Release Candidate 1 is available
The first release candidates for the 1.89.0 release are now available at: <https://archives.boost.io/release/1.89.0/source/> The SHA256 checksums are as follows: d8b0c1d593d68fe359616aa2fae4b3e258ca1f90ed57eb46c5494c29cdd1d49d boost_1_89_0_rc1.7z 9de758db755e8330a01d995b0a24d09798048400ac25c03fc5ea9be364b13c93 boost_1_89_0_rc1.tar.gz 85a33fa22621b4f314f8e85e1a5e2a9363d22e4f4992925d4bb3bc631b5a0c7a boost_1_89_0_rc1.tar.bz2 77bee48e32cabab96a3fd2589ec3ab9a17798d330220fdd8bde6ff5611b4ccde boost_1_89_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
On Aug 7, 2025, at 9:05 AM, Marshall Clow <mclow.lists@gmail.com> wrote:
The first release candidates for the 1.89.0 release are now available at: <https://archives.boost.io/release/1.89.0/source/>
The SHA256 checksums are as follows:
d8b0c1d593d68fe359616aa2fae4b3e258ca1f90ed57eb46c5494c29cdd1d49d boost_1_89_0_rc1.7z 9de758db755e8330a01d995b0a24d09798048400ac25c03fc5ea9be364b13c93 boost_1_89_0_rc1.tar.gz 85a33fa22621b4f314f8e85e1a5e2a9363d22e4f4992925d4bb3bc631b5a0c7a boost_1_89_0_rc1.tar.bz2 77bee48e32cabab96a3fd2589ec3ab9a17798d330220fdd8bde6ff5611b4ccde boost_1_89_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 built the libraries on a M4 Mac Mini running Mac OS Sequoia 15.5 (24F74) using 'Apple clang version 17.0.0 (clang-1700.0.13.5)’ All the libraries built successfully on C++11/14/17/20/23/2c — Marshall
On Aug 7, 2025, at 9:05 AM, Marshall Clow mclow.lists@gmail.com wrote:
The first release candidates for the 1.89.0 release are now available at: https://archives.boost.io/release/1.89.0/source/
The SHA256 checksums are as follows:
d8b0c1d593d68fe359616aa2fae4b3e258ca1f90ed57eb46c5494c29cdd1d49d boost_1_89_0_rc1.7z 9de758db755e8330a01d995b0a24d09798048400ac25c03fc5ea9be364b13c93 boost_1_89_0_rc1.tar.gz 85a33fa22621b4f314f8e85e1a5e2a9363d22e4f4992925d4bb3bc631b5a0c7a boost_1_89_0_rc1.tar.bz2 77bee48e32cabab96a3fd2589ec3ab9a17798d330220fdd8bde6ff5611b4ccde boost_1_89_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 an M4 Macbook Pro running macOS Sequioa 15.6 (24G84) with Homebrew Clang 20.1.8 and cxxstd=11,14,17,20,23,2c. The previously reported configuration issue with Boost.Context remains [1] so Cobalt, Context, Coroutine, Fiber, and Process all fail. Log failed to build in the beta, but it builds fine now since Andrey dropped the dependency on Context [2]. Matt [1] https://lists.boost.org/archives/list/boost@lists.boost.org/message/UXB2E4IT... [2] https://lists.boost.org/archives/list/boost@lists.boost.org/message/326XDO6U...
On Thu, Aug 7, 2025 at 11:05 AM Marshall Clow via Boost < boost@lists.boost.org> wrote:
The first release candidates for the 1.89.0 release are now available at: <https://archives.boost.io/release/1.89.0/source/>
The SHA256 checksums are as follows:
d8b0c1d593d68fe359616aa2fae4b3e258ca1f90ed57eb46c5494c29cdd1d49d boost_1_89_0_rc1.7z 9de758db755e8330a01d995b0a24d09798048400ac25c03fc5ea9be364b13c93 boost_1_89_0_rc1.tar.gz 85a33fa22621b4f314f8e85e1a5e2a9363d22e4f4992925d4bb3bc631b5a0c7a boost_1_89_0_rc1.tar.bz2 77bee48e32cabab96a3fd2589ec3ab9a17798d330220fdd8bde6ff5611b4ccde boost_1_89_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
Looks good on windows/visual studio. toolset arch compile Link Execute 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. Output here: https://gist.github.com/teeks99/a3e110374cf080debe94506149ce6d3f Tom
There are no tags in the repository of individual libraries for this version. I'd like to test building the new version of Boost in the VSPG package manager. It uses CMake and separate Github repositories. Yury.
There are no tags in the repository of individual libraries for this version.
The 'master' branch is locked during the release window. You can check out all the libraries matching this version: git clone -b master https://github.com/boostorg/boost cd boost git submodule update --init
VCPKG does not use a monorepo. All previous versions had tags. Even the website contains broken links. For example, see the source code link at https://www.boost.org/library/1.89.0.beta1/accumulators/ All you need to fix this is to create tags on Github. Yury. On Tue, 12 Aug 2025 at 14:53, Sam Darwin <samuel.d.darwin@gmail.com> wrote:
There are no tags in the repository of individual libraries for this version.
The 'master' branch is locked during the release window. You can check out all the libraries matching this version: git clone -b master https://github.com/boostorg/boost cd boost git submodule update --init
VCPKG does not use a monorepo.
OK, so there are two separate issues... - In terms of "broken links", yes the libraries are missing the boost-1.89.0.beta1 tag. That ought to be added. The release managers should check that step. - This message thread is about "[release] Boost 1.89.0 Release Candidate 1 is available". A release candidate is not a beta, it's similar but different. In the brief time window in between the beta and the full release, you can check out the 'master' branch of any individual library in order to get a copy of the 'Release Candidate 1' code. The git "tag" right now is just the master branch, and you are not prevented from checking out that code.
On Aug 12, 2025, at 6:43 AM, Yury Bura via Boost <boost@lists.boost.org> wrote:
VCPKG does not use a monorepo.
All previous versions had tags. Even the website contains broken links. For example, see the source code link at https://www.boost.org/library/1.89.0.beta1/accumulators/ All you need to fix this is to create tags on Github.
This is incorrect. None of the release candidates have been tagged. When 1.89.0 is released, it will be tagged. — Marshall
Yury.
On Tue, 12 Aug 2025 at 14:53, Sam Darwin <samuel.d.darwin@gmail.com <mailto:samuel.d.darwin@gmail.com>> wrote:
There are no tags in the repository of individual libraries for this version.
The 'master' branch is locked during the release window. You can check out all the libraries matching this version: git clone -b master https://github.com/boostorg/boost cd boost git submodule update --init
_______________________________________________ Boost mailing list -- boost@lists.boost.org To unsubscribe send an email to boost-leave@lists.boost.org https://lists.boost.org/mailman3/lists/boost.lists.boost.org/ Archived at: https://lists.boost.org/archives/list/boost@lists.boost.org/message/ERJVNZH5...
On 12 Aug 2025 16:58, Marshall Clow via Boost wrote:
On Aug 12, 2025, at 6:43 AM, Yury Bura via Boost <boost@lists.boost.org> wrote:
VCPKG does not use a monorepo.
All previous versions had tags. Even the website contains broken links. For example, see the source code link at https://www.boost.org/library/1.89.0.beta1/accumulators/ All you need to fix this is to create tags on Github.
This is incorrect. None of the release candidates have been tagged.
When 1.89.0 is released, it will be tagged.
Previous betas did have tags, but there are no boost-1.89.0.beta1 tags.
On Aug 12, 2025, at 8:18 AM, Andrey Semashev via Boost <boost@lists.boost.org> wrote:
On 12 Aug 2025 16:58, Marshall Clow via Boost wrote:
On Aug 12, 2025, at 6:43 AM, Yury Bura via Boost <boost@lists.boost.org> wrote:
VCPKG does not use a monorepo.
All previous versions had tags. Even the website contains broken links. For example, see the source code link at https://www.boost.org/library/1.89.0.beta1/accumulators/ All you need to fix this is to create tags on Github.
This is incorrect. None of the release candidates have been tagged.
When 1.89.0 is released, it will be tagged.
Previous betas did have tags, but there are no boost-1.89.0.beta1 tags.
News to me: https://github.com/boostorg/boost/releases/tag/boost-1.89.0.beta1 — Marshall
On 12 Aug 2025 18:41, Marshall Clow wrote:
On Aug 12, 2025, at 8:18 AM, Andrey Semashev via Boost <boost@lists.boost.org> wrote:
On 12 Aug 2025 16:58, Marshall Clow via Boost wrote:
On Aug 12, 2025, at 6:43 AM, Yury Bura via Boost <boost@lists.boost.org> wrote:
VCPKG does not use a monorepo.
All previous versions had tags. Even the website contains broken links. For example, see the source code link at https://www.boost.org/library/1.89.0.beta1/accumulators/ All you need to fix this is to create tags on Github.
This is incorrect. None of the release candidates have been tagged.
When 1.89.0 is released, it will be tagged.
Previous betas did have tags, but there are no boost-1.89.0.beta1 tags.
News to me:
https://github.com/boostorg/boost/releases/tag/boost-1.89.0.beta1 <https://github.com/boostorg/boost/releases/tag/boost-1.89.0.beta1>
Yes, but not in submodules.
On 12 Aug 2025 18:46, Andrey Semashev wrote:
On 12 Aug 2025 18:41, Marshall Clow wrote:
On Aug 12, 2025, at 8:18 AM, Andrey Semashev via Boost <boost@lists.boost.org> wrote:
Previous betas did have tags, but there are no boost-1.89.0.beta1 tags.
News to me:
https://github.com/boostorg/boost/releases/tag/boost-1.89.0.beta1 <https://github.com/boostorg/boost/releases/tag/boost-1.89.0.beta1>
Yes, but not in submodules.
Beta tags are still missing in submodules. Is this planned to be fixed?
On 14 Aug 2025 23:55, sam--- via Boost wrote:
Beta tags are still missing in submodules. Is this planned to be fixed?
The official 1.89.0 release is now available. Why beta tags? Those versions are immediately "obsolete".
Well, for the same reason why we have release tags - to mark the revisions that went into the beta. Yes, those are not as important and useful as the final release tags, but still. During the release process, beta tags are needed to make links to docs and sources work on the website, as evidenced by this thread. So if tagging is not somehow automated, it should be, so that we don't have this problem in the next release cycle. If it is automated, then why didn't it work this time?
On Tue, Aug 12, 2025 at 6:52 AM Yury Bura via Boost <boost@lists.boost.org> wrote:
VCPKG does not use a monorepo.
All previous versions had tags. Even the website contains broken links. For example, see the source code link at https://www.boost.org/library/1.89.0.beta1/accumulators/ All you need to fix this is to create tags on Github.
Yury.
Wow, are you actually interested in previewing Boost releases with vcpkg? I had this working a little while ago, ha ha. I put the project down because there was no user interest. Maybe I should actually pick up my nightly Boost efforts then... - Christian
I am interested in as many people as possible being able to use Boost. The vcpkg package manager greatly simplifies the connection and integration of Boost into a user's project. At the same time, it is important that new versions of Boost get into vcpkg as quickly as possible. Since there are many libraries that use and depend on Boost, the process of migrating to a new version can take a long time. Being able to start porting and testing at the beta or release candidate stage will allow us to identify and fix many problems early. I'm going to create a draft pull request in the vcpkg repository and test an unreleased version of Boost using vcpkg's internal continuous integration. Yury. On Tue, 12 Aug 2025 at 20:27, Christian Mazakas via Boost < boost@lists.boost.org> wrote:
On Tue, Aug 12, 2025 at 6:52 AM Yury Bura via Boost <boost@lists.boost.org
wrote:
VCPKG does not use a monorepo.
All previous versions had tags. Even the website contains broken links. For example, see the source code link at https://www.boost.org/library/1.89.0.beta1/accumulators/ All you need to fix this is to create tags on Github.
Yury.
Wow, are you actually interested in previewing Boost releases with vcpkg?
I had this working a little while ago, ha ha. I put the project down because there was no user interest.
Maybe I should actually pick up my nightly Boost efforts then...
- Christian _______________________________________________ Boost mailing list -- boost@lists.boost.org To unsubscribe send an email to boost-leave@lists.boost.org https://lists.boost.org/mailman3/lists/boost.lists.boost.org/ Archived at: https://lists.boost.org/archives/list/boost@lists.boost.org/message/EHJEHTOD...
On Wed, Aug 13, 2025 at 1:53 AM Yury Bura <yurybura@gmail.com> wrote:
I am interested in as many people as possible being able to use Boost. The vcpkg package manager greatly simplifies the connection and integration of Boost into a user's project. At the same time, it is important that new versions of Boost get into vcpkg as quickly as possible. Since there are many libraries that use and depend on Boost, the process of migrating to a new version can take a long time. Being able to start porting and testing at the beta or release candidate stage will allow us to identify and fix many problems early. I'm going to create a draft pull request in the vcpkg repository and test an unreleased version of Boost using vcpkg's internal continuous integration.
Btw, any update on this? Fwiw, vcpkg has a powershell script they use to update all of the ports in-place. I think what Boost should do is host an actual registry that's maintained by more than just me. I've done it before and it's actually pretty easy but I'm pretty busy nowadays and I can't reliably guarantee the ability to make sure releases happen on schedule so I'd only feel comfortable volunteering to help if I had a backup from someone else. - Christian
Christian, Maybe I could be able to help maintain the registry and alleviate your workload ? Is it related to your nightly build experiment ? Best, Arno
On Fri, Aug 22, 2025 at 5:57 AM Arnaud Becheler <arnaud.becheler@gmail.com> wrote:
Christian, Maybe I could be able to help maintain the registry and alleviate your workload ? Is it related to your nightly build experiment ?
Yup. It'd be navigating this repo: https://github.com/cmazakas/vcpkg-registry And then seeing if the patch still applies to what's current in vcpkg. Ideally, someone would be able to step in and be able to maintain the required patches we apply to the generate-ports.ps1 script. vcpkg has largely automated how they handle Boost, we just need to go in and play around with the commit hashes and the version names and whatnot. Then from there it's just about curating the registry. My original goal was nightly but eh. We should be able to play this all by ear and figure out how we'd like to carve our own releases. There's a lot of value in making nightly and beta versions of Boost widely and easily available. So yeah, a good first step would be seeing if you can either figure out what I did or come up with a better way of patching the way vcpkg generates Boost. - Christian
I worked on updating the vcpkg version and finalizing generate-ports.ps1. I can help with integration tests. In my free time, I work on updating Boost https://github.com/microsoft/vcpkg/pull/46963. At least two issues have already been discovered in the Boost libraries. Yury. On Fri, 22 Aug 2025 at 19:57, Christian Mazakas via Boost < boost@lists.boost.org> wrote:
On Fri, Aug 22, 2025 at 5:57 AM Arnaud Becheler <arnaud.becheler@gmail.com
wrote:
Christian, Maybe I could be able to help maintain the registry and alleviate your workload ? Is it related to your nightly build experiment ?
Yup. It'd be navigating this repo: https://github.com/cmazakas/vcpkg-registry
And then seeing if the patch still applies to what's current in vcpkg. Ideally, someone would be able to step in and be able to maintain the required patches we apply to the generate-ports.ps1 script.
vcpkg has largely automated how they handle Boost, we just need to go in and play around with the commit hashes and the version names and whatnot. Then from there it's just about curating the registry.
My original goal was nightly but eh. We should be able to play this all by ear and figure out how we'd like to carve our own releases.
There's a lot of value in making nightly and beta versions of Boost widely and easily available.
So yeah, a good first step would be seeing if you can either figure out what I did or come up with a better way of patching the way vcpkg generates Boost.
- Christian _______________________________________________ Boost mailing list -- boost@lists.boost.org To unsubscribe send an email to boost-leave@lists.boost.org https://lists.boost.org/mailman3/lists/boost.lists.boost.org/ Archived at: https://lists.boost.org/archives/list/boost@lists.boost.org/message/44GXCTJE...
participants (10)
-
Andrey Semashev -
Arnaud Becheler -
Christian Mazakas -
Marshall Clow -
Matt Borland -
Sam Darwin -
sam＠cppalliance.org -
Tom Kent -
Yury Bura -
yurybura＠gmail.com