Bug#1000342: bullseye-pu: package mariadb-10.5 10.5.13-0+deb11u1
> > Before I submit the final debdiff and changelog I will wait for the
> > release date to show up at https://release.debian.org/
>
> Why? The longer you wait, the fewer changes you have to actually get the update
> into the next point release. It'd be better to send those debdiffs early and
> give more time for ACKs or comments.
Last time I waited from July to September and what ended up in the
next stable update was eventually a different MariaDB release:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991221
If I send now 10.5.13+bugfixes for review but eventually we end up
uploading 10.5.14+bugfixes, then the intermediate work would be
inefficient use of time. In open source it is also important to keep
the window for contributions open and not immediately close it, in
particular if it then just remains closed for months in vain.
Therefore I will close the chapter on this release and make the final
changelog/debdiff at a time when I know that it actually is time to do
so.
It would be much easier to target a stable update if the date (or at
least the month) was published on https://release.debian.org/
Reply to: