On Fri, 2025-11-28 at 21:04 +0100, Lumír Balhar wrote: > Hi all, > > I recently discovered that we currently have 418 open Bugzillas created > by Upstream Release Monitoring, all assigned to /Orphan Owner/. These > bugs don’t seem useful to keep around, especially considering that one > of the core checks during new package reviews is verifying that the > latest upstream version is packaged—so these “update is available” bugs > for orphaned packages serve no practical purpose. > > I believe we can define additional search queries that would identify > other categories of similarly obsolete or low-value bugs. > > With that in mind, I’d like to ask: Would it make sense to introduce a > “stale bug” policy and run a cronjob or lightweight service that > automatically closes such bugs based on a set of agreed-upon rules? I > think this could help reduce noise in Bugzilla and make the remaining > issues more meaningful.
We already close bugs for EOL releases when the release goes EOL. If nobody ever bumps the bug to be for a later release, they'll get closed by that process. If someone was going to add a new process, it should follow the pattern of the existing mass bug actions like https://docs.fedoraproject.org/en-US/program_management/pgm_guide/sop/eol-day/ and extend the existing fedora_bz.py script, let's not reinvent that wheel again. -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @[email protected] https://www.happyassassin.net -- _______________________________________________ devel mailing list -- [email protected] To unsubscribe send an email to [email protected] Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/[email protected] Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
