Hi Thorsten, On 24-07-2021 00:21, Thorsten Glaser wrote: > Might be useful to script-check everything that’s newer in sid > than in testing against the open unblock requests. > I have seen > changes that are definitely targetting bullseye (RC bug python > 2 removal, in fritzing-parts, for example) where the maintainer > seems to have forgotten them (same for occasional post-NMU up‐ > loads and even binNMUs), as well as uploads for packages where > I thought they’d have unblock requests and am surprised to see > none (bash, for example). Things that we probably want to have > in the release and that went below the radar for weeks? Since mid 2020 I have been filing out-of-sync bugs [0] with a script of mine [1]. Without the check that you suggest about unblock bugs, it reports 365 packages being out-of-sync longer than 60 days. The total list is longer and not reviewable by the Release Team. The number of unblock bugs is 17. The number of blocked RC bug fixes is 7. > Actually… it might be useful if there was a tool to do that and > ping the maintainers every three days or so during the entire > freeze (including early). The annoyance of those mails might even > serve to help making maintainers avoid uploads to sid that they > don’t want to include in the release during the freeze… I know > that each time there are *way* too many of those… Sure, maybe next release. As always, patches welcome. Paul [0] I stopped after the soft freeze for hopefully obvious reasons [1] based on udd (if I copy/pasted correctly): psql service=udd -c 'select source, testing_version, unstable_version, sync from migrations where in_testing = date(now()) and date(sync) < date(now()) - 60 ;'
Attachment:
OpenPGP_signature
Description: OpenPGP digital signature