OK, so:
1) I just pushed a basic GCC15 compatibility fix which I think should be in for
the release.2) I have another one which I hesitate (basic C++11 and Java8) and
that lives for now in the compiler-101 branch.3) And then there is a wild bunch
of changes also on that branch that are not ready.
I think after the release we should just jump directly into C++17.
Still some minor details to fix (lucene) but great job everybody!
Pedro.
ps. not important, but it is somewhat weird that it's called trunk and not main
:).
On Thursday, November 5, 2026 at 06:15:39 AM GMT-5, Jim Jagielski
<[email protected]> wrote:
Since the focus is on getting AOO5 out, we should assume that anything added
to `trunk` is a candidate for backport to `AOO50X`.
If there are long-term, "experimental" work efforts, then we don't want to stop
them, but, IMO at least, maybe they should be done in branches off of `trunk`
and not folded _into_ trunk. One reason why work on 4.2.X stagnated was because
of that exact reason: that trunk and AOO42X just diverged way, way too much.
Does that make sense?
--
Jim
"Ow, chicka-chicka-ow-- OW! Man, my hat's on fire!"
- The Spirit of Jazz
