See for example https://bugzilla.redhat.com/show_bug.cgi?id=1738174 - scribus was orphaned becasue of this bugzilla. But later it was unorphaned in https://pagure.io/releng/issue/8829 - yet the bugzilla reamined asigned to the orphan.
When a releng person assigns a package, the same person should check that all bugzillas are properly assigned to the new maintainer. Either by doing it, or by asking the new maintainer to do it and only close the ticket once it is done.
Sooner the better, as always.
When there is an automation, like it once was, that says "The component changed owner" and reassigns the bugzilla automagically.
Neglected packages get orphaned, later unorphaned, but they remain neglected, because the new maintainers are not aware of the bugzillas.
I am not sure what kind of permissions one needs to reassign the bugs. We should make this part os the SOP document.
We should fix script which is (re-)assigning bugs to the PoC of a package instead.
I am not sure what kind of permissions one needs to reassign the bugs.
AFAIK There are no extra permissions needed.
Metadata Update from @humaton: - Issue assigned to humaton
Please, @mohanboddu when you reassign packages, ask the maintainers to take the bugzillas. We cannot just hand over a package that is full of CVEs to a person without them even realizing it.
@pingou Isn't our bugzilla sync script reassigning things? Or no?
I think it does now, yes.
Metadata Update from @churchyard: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
@pingou Isn't our bugzilla sync script reassigning things?
It does now yes.
Log in to comment on this ticket.