Note: Having some trouble getting the web page updated... check back
with it soon.
Please download the beta, give it a try, and report any problems you
-- The Boost Release Team
The directory is "RC1", is this the usual pre-beta RC series that we usually go through, or did the release team skip RC announcements this time?
For what its worth, this RC 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
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.
> Please download the beta, give it a try, and report any problems you
> -- The Boost Release Team
> The directory is "RC1", is this the usual pre-beta RC series that we
> usually go through, or did the release team skip RC announcements this time?
This is my mistake. The pre-beta RC series got skipped. I did a lot of
local testing and didn't fully understand the steps Marshall had been
In short, if Tom thinks this package looks good then it is also the
Beta1. Sorry about the confusion and thank you for the feedback. The
next round will be executed better.
I'm not wild about changing the release process on the fly, especially if it eliminates the community's testing of RCs. I do a bunch of tests, but they are limited to the Windows/Visual Studio configurations, there's a much more diverse audience out there that we often get feedback from.
That said, if this is Beta1, I'll upload these binaries as the windows packages to bintray. (uploading now, should be visible in a few minutes)