On Tue, Sep 20, 2022 at 10:01:36AM -0400, Ben Cotton wrote: > comps, the system of XML files used to put packages into functional > groups is hosted on a Pagure repo[1] but also has a Bugzilla > component. In the interests of simplicity, I propose to disable the > comps component and use the Pagure repo for all comps issues. In the > case where a change in comps is necessary for Bugzilla-based processes > (e.g. blockers), we can use a bug in the distribution component. > > I don't see a benefit to having the Bugzilla component for comps as a > general matter, but if there's a good argument for keeping it, let me > know. Otherwise, I plan to disable the component on Thursday 29 > September.
Amusingly I think we in the past discussed closing the pagure project to issues and using bugzilla only. ;) But I'm fine doing either one... having one place for bugs instead of two is a good thing. What will be done with the existing open bugzilla bugs? (There's some overlap between the two it looks like). Close and ask them to refile? Refile for them? kevin
signature.asc
Description: PGP signature
_______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
