On Sat, Aug 06, 2022 at 10:05:40PM +0200, Maxwell G via epel-devel wrote: > Hi EPEL folks, > > In the past couple EPEL SCo meetings, we have been discussing adding a > new package retirement policy for EPEL packages. That reads amusingly to me... to be clear 'new policy' not 'new packages'. ...snip... > > Here are my thoughts: > > If an entire Fedora package that has (an) EPEL branch(es) is orphaned, > the EPEL branch(es) should probably be orphaned at the same time as the > rawhide branch. Otherwise, we'd have to treat only orphaning an EPEL > branch as a special case: > > We could create an issue tracker for this. Packagers would have to > submit a ticket requesting to orphan a certain package's EPEL branch(es) > and set the EPEL Bugzilla assignee to "orphan" if they're orphaning all > active EPEL branches. epel-devel@ could be CC'd on all issues. Then, we > could have a provenpackager in the SIG go through and manually retire > the packages that haven't been picked up after six weeks. The later will > be difficult if we have a large volume, but I don't expect that. We > could script this if necessary or just ask the submitter to do it > themself. > > This doesn't allow picking up packages in a self-service manner, but I > don't think that's a huge deal for our case. > > > [1]: https://docs.fedoraproject.org/en-US/fesco/Policy_for_orphan_and_retired_packages/#_orphaning_and_retiring_packages I'm not sure we want to CC epel-devel on these, perhaps we could have a script that processes them once a week or so and sends a summary to the list? But I am not sure how much volume we would expect here. ;( I wonder if we could get some cycles from developers to adjust pagure-dist-git for this case to make it more self-service. (taking orphan packages over). kevin
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ epel-devel mailing list -- epel-devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to epel-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/epel-devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
