On Mon, Sep 14, 2026 at 11:58:44PM +0200, Aurelien Jarno wrote: > Hi Santiago, > > On 2026-09-14 04:13, Santiago Vila wrote: > > On Sun, Sep 13, 2026 at 11:40:41PM +0200, Aurelien Jarno wrote: > > > Adding debian-release in Cc: as the discussion concerns more than just > > > the glibc maintainers. > > > > Ok, moving to [email protected] only. > > > > > > Note that I'm not asking you to fix any of the new problems, I just > > > > wanted to raise awareness about the stability of stable. > > > > > > Stability is the wrong word here. > > > > Agreed. I meant "releasability". By "releasable" I mean following the > > release policy, including the requirement that packages in a given > > release must build in the same release (not just in a previous point > > release). > > > > Sorry, I acknowledge that this is a complex problem and also that > > there is probably not any magical solution. > > > > A simple question for the Stable Release Managers: Would you be > > willing to consider small changes in the way point releases are made? > > > > (I am thinking about deadlines, freezes, etc) > > For the record, this glibc update was accepted in trixie-p-u on July > 11th, so almost 2 months before the 13.7 point release. In that case, > there was plenty of time to detect and fix the issue, without having to > change the deadlines. > > For sure if we have a way to catch issues before the point release, we > might want to adjust the process to detect all cases, even one accepted > close to the deadline, but we are not even there yet.
Something like [1] would be the kind of change to the point release process that could catch such issues (including the Python breakage in the previous point release). > Regards > Aurelien cu Adrian [1] https://lists.debian.org/debian-release/2026/07/msg00928.html
