I think we could just tell the user that a component is retired by changing the component name to name(retired) or maybe some other means .
The gist is to tell the user that the component is retired and is probably not the one that is causing the bug and maybe point to other components which might be causing the issue .
Removing the component may be another way to go about it .Maybe retire it at first and remove it after some time just in case someone wants to revive the package .
Harsh
On Wed, Feb 26, 2020 at 9:46 PM Pavel Raiskup <praiskup@xxxxxxxxxx> wrote:
I today tried to mimic something that random Fedora user can do, and I
submitted bug against one of our long-time retired components. I haven't
been warned at all that the package is dead.
As user, it is easy to pick a wrong component when filling a bug - but the
problem with orphaned/retired packages is that nobody listens there
usually. Only 'Orphan Owner <extras-orphan@xxxxxxxxxxxxxxxxx>'.
Should such reports be kindly closed automatically by some bot, so user
can reopen against different component? Or should we drop the component
from bugzilla?
Pavel
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
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/devel@xxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx 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/devel@xxxxxxxxxxxxxxxxxxxxxxx
