On 17/05/25 at 02:53 +0200, Cyril Brulebois wrote: > Santiago Vila <sanv...@debian.org> (2025-05-17): > > El 17/5/25 a las 1:13, Cyril Brulebois escribió: > > > Soren Stoutner <so...@debian.org> (2025-05-05): > > > > Filing these bug reports sounds like a good idea to me. I don’t see > > > > any reason to wait as these will be severity:minor, so they won’t > > > > interfere with the trixie release. > > > > > > Filing now can trigger uploads to fix those minor bugs, meaning packages > > > that absolutely do not meet requirements for freeze exceptions end up in > > > unstable. Depending on circumstances, they might make migrations of other > > > packages more complicated than they need to be. > > > > > > (I'll refrain from naming a particular example, but I'm aware of one of > > > those without even searching for it, it just happened to show up on one of > > > my specific “important for the release” radars…) > > > > Hi. Discussing about the right time to report those bugs does not make > > much sense anymore, because Lucas already reported them :-) > > Given I mentioned spotting a resulting upload, it should be pretty clear > that I do know that has happened. > > It seemed important to me to reply to the “I don't see any reason to > wait” part (which I quoted, and kept above just in case), so that people > might take that in consideration next time they want to MBF that late in > the freeze. > > > Now we can only expect maintainers to act responsibly, and as you > > point out, be particularly careful about not affecting other packages. > > The example I was alluding to builds a udeb, and is therefore very much > not something like a leaf package one can easily pretend doesn't exist. > > > I think the idea of reporting them now was more about letting the bugs > > to be known "soon", more than starting to fix them "soon". Now we can > > forward the bugs upstream and some of the fixes will be present in the > > new upstream releases that we will start to upload after the release. > > I didn't challenge any reasons *for* filing. I'm giving a reason *not > to*, in reply to someone who said wasn't seeing any. > > Also, as a random maintainer, despite the “Severity: minor”, seeing > piles of FTBFS bug reports pop up all of a sudden in my maildir right > before entering hard freeze does not bring any kind of warm, cozy > feeling. Distraction and worry isn't quite something I enjoy. YMMV.
Sorry about that. I was kind-of expecting someone to answer "please wait" and I would have been fine with that. But I went ahead since 1) nobody replied to say so; 2) my own incentive for doing the MBF now was that I could file based on results I already had (not re-processing all packages to update results); 3) severity:minor doesn't put much pressure in fixing the issues, so I expected maintainers of important packages to wait before uploading fixes, and thus the MBF to have no impact on release tasks. But your data point shows that (3) did not hold well... Sorry! Lucas
