On 02/11/2026 12:14, Rémy Maucherat via dev wrote:
On Mon, Nov 2, 2026 at 12:41 PM Mark Thomas via dev
<[email protected]> wrote:
All,
The start of the month is here so we should be thinking about tagging
the November releases.
The various AI reviews have resulted in significantly higher numbers of
commits and PRs. There are also a handful of open bugs.
Normally, I'd aim to review all of the commits, resolve the new PRs and
the open bugs before release.
Currently, I am 2-3 weeks behind and I am unsure what to do.
Any BZ issue or PR that relates to an enhancement can wait until the
next release but that still needs those PRs and bugs to be triaged. The
commit reviews are harder. I was hoping that I'd be able to work through
them fairly quickly but that isn't the case. I am finding additional
fixes that are required or regressions quite frequently. Many of these
could be classes as no worse than the original code but there are
occasionally more serious regressions.
Yes, the extra fixes are very useful. It would be better if they were
not needed of course (working on that ...).
Thoughts?
Do we tag anyway and address regressions as they are reported?
Is there a better way to triage a large number of commits for closer review?
Does delaying the tag gain us anything?
The [VOTE] was posted on the 6th last month, so there's time.
I've caught up with all the reviews.
There is one PR that I am in the middle of reviewing that I plan to
finish today.
The i18n and library updates are done.
My plan is to run the tests over the weekend and make sure CI is clean
(or I understand why it isn't) and then tag earlyish on Monday.
Overall, nowhere near as late as I feared it might have been.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
