On 11/28/25 2:04 PM, 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.
Thanks,
Lumír
Hi,
All rawhide package bugs are already closed by my script when packages
are retired after six weeks via the orphaned packages process. There are
135 orphaned packages currently and 418 of these bugs, so obviously the
numbers don't match up. 196 of the bugs are for nodejs-* packages which
were retired and later orphaned when the Guidelines changed to bundling,
but the bugs were never closed — so those should be safe to cleanup.
There's a releng ticket somewhere to create a toddler to automatically
close bugs when packages are retired (it was linked elsewhere in this
thread) but that hasn't happened yet. I guess we should also make sure
that no packages with an active main admin have the Bugzilla assignee
override set to orphan (I tried to do that, but then came across [1]).
Other than that, I think the current practice of marking these bugs with
FutureFeature and not closing them at EOL like other bugs makes sense,
as the bugs are not specific to a single Fedora release.
Best,
Maxwell
---
[1] https://pagure.io/fedora-infrastructure/issue/12949
Numbers found using the following python-bugzilla query:
{
"columnlist":
"product,component,assigned_to,status,summary,last_change_time,severity,priority",
"email1": "[email protected]",
"email2": "[email protected]",
"emailassigned_to2": "1",
"emailreporter1": "1",
"emailtype1": "equals",
"emailtype2": "equals",
"include_fields": [
"id",
"product",
"component",
"assigned_to",
"status",
"summary",
"last_change_time",
"severity",
"priority"
],
"product": "Fedora",
"query_format": "advanced",
"status": [
"__open__"
],
"limit": 1000
}
--
_______________________________________________
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
