- Boost - lists.preview.boost.org

release clang++ std=c++23/26 trunk version emit diagnostics errors on #include <boost/program_options.hpp>
by Bjørn Roald 17 Mar '24

17 Mar '24

https://gcc.godbolt.org/z/d3PTjdMhr this is fixed by changing suspect throw() declarations with BOOST_NOEXCEPT I have not checked rest of boost for diagnostics with this compiler, but my understanding is that throw() declarations are no longer part of the standard and compilers may emit diagnostics like this. Is there any reason, except for the work to be done, not to use BOOST_NOEXCEPT everywhere? — Bjørn

2 1

Social Media Guidelines
by Vinnie Falco 16 Mar '24

16 Mar '24

I guess I'll take a stab at offering a starting point for social media posting guidelines. When I had access to post to the Boost_Libraries account there were basically two kinds of posts. Official communications from the Developers, and unofficial but relevant announcements. The Developers are defined as the set of members of the boostorg GitHub organization who have the Owner role, plus any proxies they authorize. Official communications include: * When a review starts https://twitter.com/Boost_Libraries/status/1622664075217092609 * When review results are available https://twitter.com/Boost_Libraries/status/1768833941341896756 * When a Boost release is published (usually 3 a year): https://twitter.com/Boost_Libraries/status/1735542393229967849 * When a change in policy for the libraries happens: https://twitter.com/Boost_Libraries/status/1633484289693339648 Official communications are identifiable by the Boost logo watermark appearing at a prescribed location and size in the color Boost Mustard. Examples of unrelated but relevant announcements include: https://twitter.com/Boost_Libraries/status/1716891934986530946 https://twitter.com/Boost_Libraries/status/1748504615371334006 Unofficial posts should have images if possible, but never with a Boost logo watermark, to denote that the post does not presume to speak for or have an association with the Developers. Anyway, these are the set of rules I informally invented when I had posting privileges to Boost_Libraries. I always checked with other developers before posting anything, especially for unofficial posts to ensure that the content was relevant to Boost in some fashion. This could be used as the starting point for explaining the guidelines for operating official Boost accounts. There is a page in the new site docs (a work in progress for sure) which is intended to capture these guidelines in a way that is easily understood by readers: https://www.boost.io/doc/contributor-guide/tweeting.html Disclaimer: That page is probably not be up to date, and is not the product of a consensus-driven process. But it can be, someone just needs to volunteer to do the work. Thanks

1 0

Review schedule update
by Mateusz Loskot 16 Mar '24

16 Mar '24

Folks, I have just updated the review schedule with status of the reviewed libraries as well as Boost versions releasing the new libraries. I'll appreciate if authors of the libraries (from STLInterfaces onwards) could verify if I've got their release version right. p.s. thanks to Christopher Kormanyos for nudging me about the update. Best regards, -- Mateusz Łoskot - on behalf of the Review Wizards Team

2 3

Re: [boost] (Important) Boost Foundation meeting this Wednesday
by Louis Tatta 16 Mar '24

16 Mar '24

On Mon, Mar 11, 2024 at 12:23 PM David Sankel <camior(a)gmail.com> wrote: > Our monthly Boost Foundation meeting is this Wednesday at 3pm Eastern > (12pm Pacific). > To: Boost developer community and Boost Foundation Board Hi everyone, I write to address two important matters regarding recent events. First, upon reviewing my messages with David and conferring with Vinnie, I must apologize for a miscommunication. I did not realize that “copyright assignment” was a term of art which means to transfer all legal rights and title. I thought instead it meant that Boost Foundation would receive a license to reproduce the logo without permission in referential contexts. Vinnie wasn’t involved in this so it is unfair to blame him; in fact, the task of this communication was delegated to me specifically because David suggested that dealing with someone else might be preferable to dealing with Vinnie. Second, as the agenda for the Boost Foundation board meeting occurring on March 13th includes a discussion of the new website, I would reiterate our proposed contribution to the developer community. A transfer of copyrights is not in line with Boost tradition, but it is still possible for us to have a healthy relationship. Thusly we repeat our previous offer: 1. The boost.org domain will point to The C++ Alliance servers running the new website, which we will operate and pay for. 2. Administrative access to the new cloud services will include Sam Darwin (CTO of C++ Alliance), plus anyone appointed by the developer community. 3. The new Boost logo (“B Mark”) will have its copyright and trademark retained by The C++ Alliance, and it will be published under a license which allows for irrevocable, permissionless reproduction in the context of referring to the Boost Libraries. The text for this is being prepared by our legal team, and it will be similar to the wording found under “Foundation name and C++ logo” here https://isocpp.org/home/terms-of-use. 4. Work on the website and documentation will continue in the repositories now under control of the developer community at https://github.com/boostorg/website-v2 and https://github.com/boostorg/website-v2-docs and licensed under the BSL. 5. If and when the developer community feels that the new website, infrastructure, or level of support received does not meet with expectations, the boost.org domain can be pointed away from The C++ Alliance servers. We believe this proposal is fair, generous, and respectful to tradition. It honors contributors by empowering them to continue their work, in a way that preserves the independence of the Boost project. Thank you for your consideration in this matter. Louis Tatta CEO, The C++ Alliance, Inc.

8 17

Suspicious changes to Serialization
by Peter Dimov 14 Mar '24

14 Mar '24

The current Serialization emits the following warning: c:\projects\boost-root\boost\serialization\extended_type_info_typeid.hpp(118) : warning C4700: uninitialized local variable 'ap' used which looks legitimate and is caused by the removal of `va_start(ap, count);` in this commit https://github.com/boostorg/serialization/commit/2805bc3faa8f8fb7ce80ec5181… This looks like a mistake to me, and is probably going to cause problems.

3 3

[release] Boost 1.85.0 beta 1 is available
by Marshall Clow 14 Mar '24

14 Mar '24

Boost release 1.85.0 beta 1 is now available at: https://boostorg.jfrog.io/artifactory/main/beta/1.85.0.beta1/source/ The SHA256 checksums are: c13b76f420684a8d5b2eb0f297c281348ba0311d50354d952c5ce7c689e7879b boost_1_85_0_b1.zip e65d529023c7b08d0b92c53fff24ce9df9568cc0fe667c90caf8a9dbc5e63b0d boost_1_85_0_b1.7z 9c1ce4793342e8e57eb34c61f774a9dac0c6fc036084785e416613a18091bacc boost_1_85_0_b1.tar.gz cf7449faedeac9b76bade8ee59007cc4456a14de375dfcbd9e6e38aabe8a1334 boost_1_85_0_b1.tar.bz2 There was one problem reported during the beta release process; when you build the release using b2, it will emit a warning: [errno 2] failed to scan file '': No such file or directory This is harmless, and will be fixed for the final release. the release notes are available at: https://www.boost.org/users/history/version_1_85_0.html Please try the beta and report any problems you encounter. Thanks to everyone who contributed to the release. -- Boost Release Team

3 4

Github releases for CI
by Peter Dimov 14 Mar '24

14 Mar '24

In addition to the CMake releases on Github, I've modified the action to also create releases for use with b2 (with the headers copied to boost/ and removed from libs/*/include, but without the documentation.) These would be useful for CI, which would hopefully lower the pressure on the official downloads. E.g. https://github.com/boostorg/boost/releases/tag/boost-1.85.0.beta1

1 0

[release] Boost 1.85.0 Release Candidate 1 is available.
by Marshall Clow 12 Mar '24

12 Mar '24

Available at: <https://boostorg.jfrog.io/artifactory/main/beta/1.85.0.beta1/source/> The SHA256 checksums are as follows: fa31215de3a4d2d010c0bc6e42cc63da76be82899f145ea6a6034b5bf3e6e297 boost_1_85_0_b1_rc1.zip 3b16d693acd4ee1745b0d9267555f7e34387527a02817f0c81bf8ec963b7c569 boost_1_85_0_b1_rc1.tar.bz2 20c7d2ccbbddeb56e618aa80960ea4dd38cbc4912b9a05fefef31c290519154e boost_1_85_0_b1_rc1.7z 7a28cd03e8e48b59a898900c953a9194b8f1efbb8c6149703b7faf08642c0cf7 boost_1_85_0_b1_rc1.tar.gz 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

8 17

Reminder: Review for Zach's parsing library starts on Feb 19th
by Marshall Clow 11 Mar '24

11 Mar '24

That’s a week from now. Github: https://github.com/tzlaine/parser Docs: https://tzlaine.github.io/parser — Marshall

14 54

[release] Request to merge B2
by René Ferdinand Rivera Morell 11 Mar '24

11 Mar '24

Can I merge the latest, 5.1.0 (a), release of B2 to master at the next opportunity? By next opportunity I mean whenever the release managers think it's appropriate. :-) [a] Release notes: <https://github.com/bfgroup/b2/releases/tag/5.1.0> -- -- René Ferdinand Rivera Morell -- Don't Assume Anything -- No Supone Nada -- Robot Dreams - http://robot-dreams.net

2 1