Automatic close of bugs for retired packages?

[Pavel Raiskup]

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(a)fedoraproject.org&gt;&#39;.

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

[Harsh Jain]

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(a)redhat.com&gt; 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(a)fedoraproject.org&gt;&#39;.
>
>  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(a)lists.fedoraproject.org
>  To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
>  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/[e-mail]
>

[Ben Cotton]

Components can be marked inactive in Bugzilla, which I believe will prevent
users from filing new bugs without losing any historical data. Perhaps this
should be part of the retirement process?

-- 
Ben Cotton
He / Him / His
Senior Program Manager, Fedora & CentOS Stream
Red Hat
TZ=America/Indiana/Indianapolis

[Miro Hrončok]

On 26. 02. 20 19:38, Ben Cotton wrote:
>  Components can be marked inactive in Bugzilla, which I believe will
> prevent 
>  users from filing new bugs without losing any historical data. 
Correct. We have done this with the "python" component.

-- 
Miro Hrončok
--
Phone: [phone]
IRC: mhroncok

[Kevin Fenzi]

On Wed, Feb 26, 2020 at 07:47:24PM +0100, Miro Hrončok wrote:
>  On 26. 02. 20 19:38, Ben Cotton wrote:
>  > Components can be marked inactive in Bugzilla, which I believe will
>  > prevent users from filing new bugs without losing any historical data.
>  
>  Correct. We have done this with the "python" component. 
We actually automatically do this now on package retirement. 

However, we haven't (yet) gone back and set all the old retired packages
this way. 

https://pagure.io/fedora-infrastructure/issue/8707 

tracks that work. 

kevin