Plans for 3.3.2 on 3/3

[Vadim Zeitlin]

Hello,

I'm afraid I'm not going to be able to do much about the remaining
problems until the planned 3.3.2 release date on 2026-03-03, but I think
it's still worth making it, even if it almost surely means that we'll need
at least one more 3.3.x release before 3.4.0.

So I'd like to prepare the sources for the release on Feb 28 to leave at
least a couple of days for testing. This, of course, leaves very little
time before the release but from past experience it looks like most bugs
will be found after making it anyhow, so it's arguably not that important.

I also wonder if we should make 3.2.10 on the same day. On one hand, there
were very few changes since 3.2.9, but OTOH it would make it simpler to say
in the release notes that 3.3.2 contains all the fixes from 3.2.10 plus the
list of new features rather than saying that it contains all the fixes from
3.2.9, plus some more fixes and new features on top of this. And the last
couple of 3.2.x releases were pretty uneventful, so maybe it's not that
crazy to make both of them at once?

As usual, please let me know what do you think and if there is anything
that you believe absolutely must be included in this release. Personally,
I'd really like to do something #26081 (Surprising wxAuiNotebook split
behaviour) and maybe related #26113 (Regression in wxAUI layout), but I'm
not sure I'm going to succeed because wxAUI code is strongly resilient to
any small local modifications and even I am not crazy enough to start
making major changes in it just before a release.

Thanks!
VZ

[Danny Scott]

I'm OK with making binaries for both on the 28th.

Danny