March 2026 - Boost - lists.boost.org

Support status for C++03 (std=c++03) in Boost [Version] on RHEL 9
by Piyush Anand 16 Apr '26

16 Apr '26

Hello Boost Community, I am currently planning a large-scale migration of a legacy codebase from SourcePro Rogue Wave to Boost. Due to strict production requirements, we must maintain the -std=c++03 flag across environments: RedHat 9 (GCC 5.x) My Question: Is there any version of Boost, which can be considered the "Long Term Support" equivalent for C++03, for which Boost also release latest patch or security vulnerabilities or actively maintain that version? From older post/blogs, it seems Boost does not manage c++03 standard and provide support of latest standard of c++ only i.e. C++14 and so on. Thanks And Regards, Piyush

5 6

[release] Master branch is now open for bug fixes
by Marshall Clow 14 Apr '26

14 Apr '26

Hi, The master branch is now open for bug fixes, test and documentation changes, but please follow the policy described in: https://github.com/boostorg/wiki/wiki/Releases%3A-Beta-Merge-Policy The next deadline: On April 1st, the master branch closes for all changes. As always, the calendar is at https://www.boost.org/calendar — The release managers

8 19

Proposing statsort for Boost.Sort
by Peter Taraba 09 Apr '26

09 Apr '26

7 17

std::core_dump() Issue 2 — Now Focused on the Boost Community
by Mark Cooper 08 Apr '26

08 Apr '26

Hi all, Issue 2 of the std::core_dump() newsletter is out: https://dl.cpp.al/newsletters/boost-newsletter-2026-03.pdf We've expanded the newsletter's focus from C++ Alliance news to the Boost community as a whole. Highlights: - Boost.URL constexpr URL parsing — malformed literals now fail at compile time, not runtime - Boost Docs Localization Pipeline — translation workflow piloted on Boost.JSON and Boost.Unordered If you'd like to contribute to next month's issue, reach out! Mark

1 1

One-time change to the release schedule (two week delay)
by Marshall Clow 26 Mar '26

26 Mar '26

Due to schedule conflicts with the release manager, we are going to postpone the 1.91.0 release for two weeks. I will be updating the calendar later today, but the important dates are: 15-Apr: Master branch closes for the 1.91.0 release 22-Apr: Scheduled release date Note that we’re currently in the post-beta period, so the following caveats still apply: Release open for bug fixes and documentation updates. Other changes by permission of a release manager. Requests to merge changes may be delayed during the week of April 6-10th. I apologize for the inconvenience. — Marshall (for the release managers)

1 0

[Regex] \r matching \n
by Olaf van der Spek 25 Mar '26

25 Mar '26

Hi, In this regex the \n matches \r. How is this defined / controlled? Is there a way to only match \n? std::string s = "[*] A\rB\n"; s = boost::regex_replace(s, boost::regex(R"(\[\*\](.+?)(\n|$))"), "<li>\\1</li>"); std::println("{}", js_encode(s)); // <li> A</li>\rB\n Regards, -- Olaf

4 8

A proposal to delay the Boost release for two weeks
by Marshall Clow 24 Mar '26

24 Mar '26

We have a small problem. Almost all of the release managers will be AFK for the week after Easter, which is the week when we’re scheduled to release 1.91.0 The current schedule is: 1-Apr: Master branch closed 2-Apr: RC1 created 8-Apr 1.91.0 released (assuming no problems) I propose to move all of those dates back two weeks. 15-Apr: Master branch closed 16-Apr: RC1 created 22-Apr 1.91.0 released (assuming no problems) Comments? — Marshall

3 2

Re: Multi Review Result
by Alfredo Correa 19 Mar '26

19 Mar '26

> Date: Mon, 16 Mar 2026 17:51:42 +0000 > From: Matt Borland <matt(a)mattborland.com> > Subject: [boost] Multi Review Result > To: "boost(a)lists.boost.org List" <boost(a)lists.boost.org> > Message-ID: <4otKiL_qCApAgTgtXPKXThbIFKkLIMk63P8vVM0NE-IthZzhBzta1GqWe > wIMTuvg8hFOGRr5ZFCP8X1xrlGJtF0KwrRIZYP-AGw2CLJlKp8=@ > mattborland.com> > Content-Type: multipart/signed; protocol="application/pgp-signature"; > micalg=pgp-sha512; > boundary="------c6d2e97bdd1cf2c5b6caf1a740c0085a140 > 8fcbcdd2b5dfcc2147cf72c1a1483"; charset=utf-8 > > Bottom Line Up Front: The library is conditionally accepted. > Thank you again to everyone who participated in the review. > Thank you all for your important reviews; they are very valuable to me. I know many people spend many hours on this. Special thanks to Matt for managing this review, with whom I will coordinate the next steps. In the coming weeks, I am going to work intensively on revamping the Reference section of the documentation, making other tweaks, and preparing a presentation. Thank you, Alfredo

2 1

Farewell to Wowbagger - End of an Era for boost.org
by René Ferdinand Rivera Morell 18 Mar '26

18 Mar '26

Dear Boost developers and community, On behalf of the Fiscal Sponsorship Committee, I'm writing today with a mix of gratitude and nostalgia to share some news: after 15 years of faithful, but rocky, service, wowbagger - the server that hosted boost.org, lists.boost.org, and subversion - is being mothballed. For many of us, it was simply there - one of those invisible pillars that kept our community connected and our work accessible to the world. It deserves a proper send-off. What happened: Rackspace recently notified customers that pricing on their legacy cloud platform is increasing significantly - effectively doubling - as they wind down the previous generation of cloud servers in favor of their next-generation platform. Migration is not automatic. After consulting with Marshall and others, we made the decision to terminate our Rackspace instances rather than absorb the increased costs or undertake a manual migration to a platform we no longer need. What this means: We (i.e. Sam Darwin) have stopped wowbagger for now. File-level backups and disk snapshots are in hand. After another week, the server will be deleted. This is purely a housekeeping matter - boost.org and lists.boost.org are already running on new, upgraded hardware and have been for some time. The old machine had been kept around as a reference for comparing web pages between the old and new sites, but the Rackspace pricing change simply accelerates a retirement that was already overdue. Nothing changes for us. The website and mailing lists continue to operate normally on their new home. Still, we wanted to take a moment to honor wowbagger's long run. 15 years is a remarkable tenure for any server, and this one carried the public face of Boost for all of that time. To everyone who set it up, maintained it, patched it at odd hours, and kept it humming along - thank you. Your work mattered more than most people ever realized. Rest well, wowbagger. You've earned it. Warm regards, Boost Fiscal Sponsorship Committee (Ion Gaztañaga, Joaquín M López Muñoz, René Ferdinand Rivera Morell)

1 0

Multi Review Result
by Matt Borland 17 Mar '26

17 Mar '26

Bottom Line Up Front: The library is conditionally accepted. Thank you again to everyone who participated in the review. For transparency, the final tally of ACCEPT/CONDITIONAL ACCEPT/REJECT, from both private and public reviews, was 1/5/2. Both rejections and nearly all conditional acceptance conditions revolved around the state of the documentation and naming. I have consolidated these conditions and related discussion on the GitHub issue tracker, rather than reiterating them here. The total number of new issues from the review period is 25. Rainer and Peter Turcan both brought up bugs or additional features for the website. I am working to address those separately with the web devs. This leads us to the singular condition of acceptance being to address the documentation related issues. Since this is a rather subjective requirement, we will be running a mini review of the library documentation in a few weeks. Several of those who conditionally accepted or rejected said they would be willing to look at the library again. This mini review period provides them a good opportunity to do so. I think this second review will give the best possible product for the initial release of Multi in Boost. Stay tuned for those dates. Thank you again for your time and participation in this review. The library is certainly better for it. Matt

3 3