Re: Orphaning EPEL Branches

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, Aug 23, 2022 at 8:42 PM Maxwell G via epel-devel
<epel-devel@xxxxxxxxxxxxxxxxxxxxxxx> 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@xxxxxxxxx> 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.
> >
> > https://pagure.io/epel/package-orphan-requests
>
>
> 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.


-- 
真実はいつも一つ!/ Always, there's only one truth!
_______________________________________________
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




[Index of Archives]     [Fedora Announce]     [Fedora News]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Maintainers]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [Fedora Fonts]     [ATA RAID]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Announce]     [SSH]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora QA]     [Fedora Triage]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Tux]     [Yosemite News]     [Linux Apps]     [Gnome Users]     [KDE Users]     [Fedora Tools]     [Fedora Art]     [Fedora Docs]     [Maemo Users]     [Asterisk PBX]     [Fedora Sparc]     [Fedora Universal Network Connector]     [Fedora ARM]

  Powered by Linux