On Nov 22, 2025, at 8:28 AM, Christian Granzin via Boost <boost@lists.boost.org> wrote:
Am 13.11.2025 um 16:50 schrieb Marshall Clow via Boost:
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 December 3rd, master closes for all changes.
As always, the calendar is at https://www.boost.org/calendar
— The release managers
Hi Marshall,
another newcomer here :-)
Welcome, Christian!
I would like to merge a bugfix in MSM, which resolves an issue related to orthogonal regions caused by a deviation from the UML StateMachine specification. The implementation has been adapted to match the specification, which also resolves the infinite recursion problem described in the GitHub issue.
- Issue: https://github.com/boostorg/msm/issues/72 - Fix: https://github.com/boostorg/msm/commit/158beca9aa0a08f83e005e536fd9bae21637d...
The change is not trivial but API-wise backwards-compatible. Though it anyway only affects a new back-end, which is available for the first time in this Boost release.
After looking at the diff, I concur that the change is definitely not trivial. Since you’re new, I’m going to pontificate here a bit - apologies if you’ve heard this all before. The goal of the period between beta and release is to increase stability, fix bugs and polish documentation. Things that decrease stability (including, but not limited to breaking existing code) can usually be delayed to the next release (which is in 4 months). Is the backMP11 back end new for the 1.90 release? Does this change affect other (existing) backends? (Since the bug was reported against 1.84, I think the answer is “yes”) What’s the status of the test runners (and CI runs)? Are they all green? — Marshall