On Tue, Aug 23, 2022 at 8:42 PM Maxwell G via epel-devel epel-devel@lists.fedoraproject.org wrote:
On Wednesday, August 10, 2022 4:07:29 PM CDT Troy Dawson wrote:
On Sun, Aug 7, 2022 at 12:31 PM Kevin Fenzi kevin@scrye.com wrote:
On Sat, Aug 06, 2022 at 10:05:40PM +0200, Maxwell G via epel-devel wrote:
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.
After some discussion in our weekly EPEL Steering Committee meeting Maxwell's idea seems to lead the way. Maxwell has setup of pagure repo, to track these orphan issues. A pagure repo gives us the opportunity to have a nice README that people can see if they are unsure of the process. A pagure issue also seems more user friendly than a bugzilla. Both for the person creating the issue, and for others tracking it.
So, I've started working on this. So far, I have a structured issue template, and I've started writing a tool to go through the issues and act on them (creating an announcement, etc. While I had originally wanted to use a Pagure issue tracker, I decided to switch to Gitlab half way through. There were three reasons:
- The Pagure API does not allow tagging existing issues. I had planned to
liberally use tags to manage the issues.
What? You can do this with the "update issue information" API call: https://pagure.io/api/0/#issues-tab
This is done by the CentOS Hyperscale folks for the package-updates tracker: https://pagure.io/centos-sig-hyperscale/package-updates
The automation for it is present in that repo.