- Boost - lists.boost.org

Boost 1.86 release notes?
by Andrzej Krzemienski 25 Jul '24

25 Jul '24

Hi Everyone, Are 1.86 beta release notes available anywhere? I recall that the beta release documentation used to be put on boost.org. Regards, &rzej;

2 1

[release] Boost 1.86.0 Beta 1 Release Candidate 3 is available
by Marshall Clow 24 Jul '24

24 Jul '24

The third (and hopefully final) RC for the 1.86.0 Beta release is now available. Available at: https://archives.boost.io/beta/1.86.0.beta1/source/ The SHA256 checksums are as follows: a632d1e1465804b26f4d73112f1142c89caf74b026395df2e63a8c8972ac3ab0 boost_1_86_0_b1_rc3.tar.gz e061d83644568178ddece4bd3e241fb2656f49d6157c5d9fbff6c2fa74b1e328 boost_1_86_0_b1_rc3.zip e7f07bbc14915469b1ef80337c16e7a592f3eb547ba2cca828253c0a32372399 boost_1_86_0_b1_rc3.tar.bz2 91dcd8f980362c1c32bf8cc547c547fb02619bea877738b478c052926edc6a2d boost_1_86_0_b1_rc3.7z Changed libraries between RC2 and RC3: Boost.Process fixed some build issues on Windows 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

1 1

[release] Boost 1.86.0 Beta 1 Release Candidate 2 is available
by Marshall Clow 24 Jul '24

24 Jul '24

Available at: https://archives.boost.io/beta/1.86.0.beta1/source/ The SHA256 checksums are as follows: c62c9ab3c448ef4ed1b45f69631e3d7cc425fca96b991e5007b3af49f84344e1 boost_1_86_0_b1_rc2.zip 7e5b42428ed30a7ac9d832e9df9f5150a29d9cffe5aebde4d4c109da89f54b77 boost_1_86_0_b1_rc2.tar.gz 8718b092b37f04a739b647d154901d923fb3c3cdcff9f793d6a472e3f8e7c647 boost_1_86_0_b1_rc2.7z cd63cd3110fafbed8c196a82dd0f72c8600bc5c7fc218ede213947da3b721c06 boost_1_86_0_b1_rc2.tar.bz2 Changed libraries between RC1 and RC2: Boost.Process Boost.Odeint 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

3 3

[release] Status of the Beta release
by Marshall Clow 24 Jul '24

24 Jul '24

We’ve had some problems with the RCs for the 1.86.0 beta. The RC1 had problems with Boost.Odient and Boost.Process. We had an RC2 yesterday, but that didn’t fix all of the Boost.Process build problems. There will be an RC3 today, which (hopefully) will fix them . If nothing else is found the beta release will be Friday. — Marshall

1 0

[release[ Boost 1.86.0 Beta 1 Release Candidate is available
by Marshall Clow 23 Jul '24

23 Jul '24

Available at: https://archives.boost.io/beta/1.86.0.beta1/source/ The SHA256 checksums are as follows: 90be7ebbaf1c81a849791eb0f49d05a9ec7dbd0ec98b974dfe31d44d811e8298 boost_1_86_0_b1_rc1.7z 543ca3b743250a8b24b25c71209cf911c35613910e78a320835c21c053212ef2 boost_1_86_0_b1_rc1.tar.gz 1bf831ed717fa3e01db6c1f104b95f5a6a8d098a4cc9e61fa6eb81969c78645f boost_1_86_0_b1_rc1.tar.bz2 f739f8761bee6006c60a39fd21ed80b7b0a681c9ed448d1ae1bb28d8d8a69659 boost_1_86_0_b1_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

7 13

[Release] Master branch is closed for beta
by Marshall Clow 23 Jul '24

23 Jul '24

Master is closed for all changes. See the release schedule at: https://www.boost.org/development/index.html -- Release managers

3 4

Q2 2024 Transparency Report on Boost C++ Library
by Louis Tatta 22 Jul '24

22 Jul '24

Hello, Louis Tatta here, CEO of The C++ Alliance, Inc, a registered 501(c)(3) non-profit organization dedicated to supporting C++. This is our Q2 2024 transparency report on our charitable work for the Boost C++ Library Collection. The C++ Alliance actively seeks out highly talented and experienced C++ experts, hiring them, often full-time, so they can fully dedicate themselves to open-source projects. Our Staff Engineers maintain existing Boost libraries, develop new ones, and contribute to other Boost projects. We also employ IT experts full-time to maintain and enhance the infrastructure supporting Boost. This includes the legacy web server, the Drone continuous integration servers, deployment scripts for GitHub Actions on Boost repositories, and scripts that publish Boost releases. Additionally, we provide on-demand technical support services for Boost authors and maintainers facing infrastructure-related issues. The Boost Mailing List remains the premier venue for high-quality discussions on Boost libraries and related C++ Standards topics. The C++ Alliance continues to support the mailing lists, upgrading them to the latest Mailman version and developing an optional web-based front-end for browser-based interaction. We also manage the Official C++ Language Slack Workspace ( https://cpp.al/slack) hosting the most popular interactive discussions on Boost libraries. The C++ Alliance sponsors a paid plan to offer full history, video and audio conferencing, collaboration tools, and unlimited document storage for seventeen dedicated Boost library channels and one main Boost discussion channel. Our largest project for Q2 2024 is the ongoing development of the new Boost website. This new site will be a C++ social media portal with rich support for user-generated content and a robust back-end that provides visibility into contributions made on GitHub and the release process. Our goal is to deliver an enhanced user experience that attracts fresh talent to Boost. Notably, the website features hand-drawn graphics by our contract artist, reflecting our commitment to ensuring Boost not only functions well but also looks visually appealing. In Q2 2024 there were a total of zero Boost Formal Reviews. There were two petitions for endorsement for potential Boost candidates: *async_mqtt from Takatoshi Kondo (https://github.com/redboltz/async_mqtt) *multi from Alfredo Correa (https://gitlab.com/correaa/boost-multi) There's another MQTT library in the works proposed on Nov 2023, Async.MQTT5 from Ivica Siladic, Bruno Iljazovic and Korina Simicevic ( https://github.com/mireo/async-mqtt5) There were a total of three messages from the @Boost_Libraries X (formerly Twitter) account, all submitted by C++ Alliance team members. One of them featured artwork from Bob Ostrom, commissioned by us. Posts with visuals are three times more engaging than those with just text. We see the X platform as a vital tool for educating newer generations about the benefits of Boost. A total of $526,000 was spent on Boost-related contributions, broken down thusly (and rounded to the nearest thousand): Staff Engineers Compensation $392,000 Website Software Development $111,000 Server Hosting $23,000 During Q2 2024 we employed a total of 13 individuals to contribute to Boost. Here is a high-level summary of accomplishments: Sam Darwin (Chief Technical Officer) - Summary: Sam Darwin led major projects, overseeing the integration of new features in the Boost infrastructure. He coordinated between teams, ensuring smooth transitions and high-quality deliverables. His leadership was pivotal in the development of the new Boost website and improvements to the mailing list system. - Link: Sam Darwin's Q2 Update <https://cppalliance.org/sam/2024/07/10/SamsQ2Update.html> Dmitry Arkhipov (Staff Engineer) - Summary: Dmitry Arkhipov focused on maintaining and enhancing Boost libraries. He implemented several bug fixes, optimized existing code, and contributed to the development of new libraries. Dmitry also played a significant role in the continuous integration and deployment processes. - Link: Dmitry Arkhipov's Q2 Update <https://cppalliance.org/dmitry/2024/07/12/dmitrys-q2-update.html> Alan de Freitas (Staff Engineer) - Summary: Alan de Freitas worked extensively on the Boost website redesign, particularly on the back-end systems that support user-generated content and GitHub integration. He also contributed to developing new libraries and maintaining existing ones. - Link: Alan de Freitas's Q2 Update <https://cppalliance.org/alan/2024/07/13/AlanQ2Update.html> Christian Mazakas (Staff Engineer) - Summary: Christian Mazakas worked on enhancing Boost’s infrastructure, including optimizing server performance and improving deployment scripts. His contributions were crucial for maintaining the stability and efficiency of the Boost libraries. - Link: Not provided. Krystian Stasiowski (Staff Engineer) - Summary: Krystian Stasiowski focused on developing new features for existing Boost libraries and worked on performance optimizations. His work included contributing to the ongoing development of new libraries and providing technical support to other Boost authors. - Link: Krystian Stasiowski's Q2 Update <https://cppalliance.org/krystian/2024/07/15/KrystiansQ2Update.html> Peter Turcan (Senior Technical Writer) - Summary: Peter Turcan was responsible for creating and updating documentation for Boost libraries. He ensured that all new features and libraries were well-documented, making it easier for users to understand and utilize Boost’s capabilities. - Link: Peter Turcan's Q2 Update <https://cppalliance.org/peter/2024/07/07/PeterTurcan-Q2-2024.html> Matt Borland (Staff Engineer) - Summary: Matt Borland contributed to the development of new libraries and enhancements to existing ones. His focus was on improving library performance and ensuring that the codebase remained robust and reliable. - Link: Matt Borland's Q2 Update <https://cppalliance.org/matt/2024/07/08/Matts2024Q2Update.html> Ruben Perez (Staff Engineer) - Summary: Ruben Perez worked on several infrastructure projects, including server maintenance and optimization. He also contributed to the development and maintenance of Boost libraries, focusing on performance improvements and bug fixes. - Link: Ruben Perez's Q2 Update <https://cppalliance.org/q2_update/2024/07/09/RubenQ2.html> Mohammad Nejati (Staff Engineer) - Summary: Mohammad Nejati was involved in developing new libraries and improving existing ones. He focused on optimizing code and ensuring that Boost libraries were efficient and reliable. His work also included providing technical support to other developers. - Link: Mohammad Nejati's Q2 Update <https://cppalliance.org/mohammad/2024/07/10/MohammadsQ2Update.html> Fernando Pelliccioni (Staff Engineer) - Summary: Fernando Pelliccioni contributed to the ongoing development of the Boost libraries, focusing on implementing new features and optimizing performance. His work was instrumental in ensuring the high quality and reliability of Boost libraries. - Link: Fernando Pelliccioni's Q2 Update <https://cppalliance.org/fernando/2024/07/08/FernandoQ2Update.html> Joaquin M Lopez Munoz (Staff Engineer) - Summary: Joaquin M Lopez Munoz worked on several key projects, including the development of new Boost libraries and enhancements to existing ones. His contributions focused on improving code efficiency and performance. - Link: Joaquin M Lopez Munoz's Q2 Update <https://cppalliance.org/joaquin/2024/07/06/Joaquins2024Q2Update.html> Kenneth Reitz (Staff Engineer) - Summary: Kenneth Reitz focused on developing and maintaining Boost libraries, implementing new features, and optimizing existing code. His work also involved providing technical support and contributing to the Boost website redesign. - Link: Kenneth Reitz's Q2 Update <https://cppalliance.org/kenneth/2024/07/12/KennethQ2Update.html> Braden Ganetsky (Junior Staff Engineer) - Summary: Braden Ganetsky, as a junior engineer, contributed to various Boost library projects. His work included implementing new features, fixing bugs, and assisting with infrastructure maintenance. Braden’s contributions were valuable in supporting the overall development efforts. - Link: Braden Ganetsky's Q2 Update <https://cppalliance.org/braden/2024/07/14/BradenQ2Update.html>

6 8

Modular Boost status..
by René Ferdinand Rivera Morell 21 Jul '24

21 Jul '24

Yesterday I created PRs for each library that introduces the changes to build (and some code) to implement the modular B2 building. I track all the PRs here: <https://github.com/users/grafikrobot/projects/1/views/2> All the library PRs are in Draft status, as we wait for the tool related PRs to get merged. You can read an explanation of the changes here <https://github.com/grafikrobot/boost-b2-modular/blob/b2-modular/README.adoc> (the explanations may differ slightly from current reality). IMPORTANT: The PRs are all "Draft" as I continue to monitor build errors from any CI errors in the PRs. And to address feedback from authors. After the current release the process will go something like this: * I fix any current fallout in draft PRs. * The 1.86 release happens. * The owners merge the tool PRs to develop and master. * I fix any fallout from that. * Authors, and owners, merge library PRs to develop and master. * I fix any fallout from that. * I create subsequent PRs for the global B2 Boost build infrastructure to remove the old non-modular dead code. * The 1.87 release happens. Questions? -- -- René Ferdinand Rivera Morell -- Don't Assume Anything -- No Supone Nada -- Robot Dreams - http://robot-dreams.net

1 0

[compute] Maintenance status
by Joaquin M López Muñoz 21 Jul '24

21 Jul '24

It was brought to my attention that Boost.Compute seems to be all but abandoned: no updates in three years, more than 100 issues filed, 27 unattended PRs. This is a shame given that the library looks pretty popular based on GH stars and references on Internet. Are there volunteers to take on maintenance of the library? Best, Joaquin M Lopez Munoz

1 0

Should include of quadmath.h in multiprecision/cpp_bin_float.hpp be guarded with ifdef BOOST_MATH_HAS_QUADMATH_H?
by Martin Jambor 19 Jul '24

19 Jul '24

Hello, because of a bug[1] in GCC 13 and earlier versions, the #include of quadmath.h in multiprecision/cpp_bin_float.hpp did not fail even when the header file was not present on the system and compilation succeeded as long as nothing from the header file was actually needed. The bug has been fixed in GCC 14 which all of a sudden leads to new build requirements and failures such as [2]. Examining this build failure, I noticed that in math/special_functions/fpclassify.hpp (which is indirectly included from multiprecision/cpp_bin_float.hpp) the existence of the header file is specifically tested and macro BOOST_MATH_HAS_QUADMATH_H is defined or not accordingly. So I wanted to ask the question in the $subject. Could, or perhaps even should the include (together with its uses introduced in commit 4911125248bd) be guarded also by BOOST_MATH_HAS_QUADMATH_H and not just by BOOST_HAS_FLOAT128? Thank you, Martin [1] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80753 [2] https://bugzilla.opensuse.org/show_bug.cgi?id=1225861#c7

2 1