This has come up during the f42 mass rebuild, see: https://pagure.io/releng/issue/12527#comment-951850
It looks like there are ~100 package repositories that were never touched other than the initial repo creation. I propose that packages that have been in this state for more than (period of time to be determined) are explicitly retired (after sending the list to the devel list and waiting for people to wake up from their winter sleep, of course).
There are also a number packages in this list that appear to be EPEL-only. Maybe the guidelines for creation of EPEL-only packages need to be amended to make it clear that their rawhide branch must be retired?
We should definitely do the retirement.
Proposal: Releng shall retire package repositories that didn't have any content imported for a month after repo creation. A notification shall be sent to fedora-devel. This retirement procedure shall be repeated as releng finds appropriate.
For the EPEL guideline change: https://pagure.io/fedora-docs/package-maintainer-docs/pull-request/174
Orphaned packages that are up for retirement (a similar situation) are retired after 6 weeks, with weekly reminders, I think it would make sense to apply similar rules here.
+1 for the docs update, though you submitted the PR to the Packager Maintainer docs, not to EPEL guidelines :)
Orphaned packages presumably have some users and history and in general are worth something. Packages that were never imported don't IMO need to be treated particularly carefully. I don't think we want to send more than one reminder for them.
you submitted the PR to the Packager Maintainer docs, not to EPEL guidelines
Yes. But the EPEL guidelines heavily refer to the Package Maintainer docs. I bounced around the various pages for a while before I settled on the two spots in the pull request. But if there's a better place, or an additional place to modify, I'm all ears.
This has been stalled for a week now. Everyone except Fabio, please review/comment/vote.
+1 on @zbyszek proposal and doc update
+1 here. Would be great to get these cleaned up.
+1
After a week, as per FESCo voting rules, this request is now marked as APPROVED (+5, 0, 0)
Metadata Update from @kevin: - Issue tagged with: pending announcement
Metadata Update from @kevin: - Issue close_status updated to: Accepted - Issue status updated to: Closed (was: Open)
It looks like the vote was counted for this proposal? I explicitly only said +1 for the EPEL docs update, so I only count +3 votes too (even counting @zbyszek as implicit +1 for his own proposal, it's only +4).
And what's the expected outcome of the vote? Add a poddler that retires packages that aren't imported within 4 weeks (or 1 month?) after being created?
Sorry about miscounting there... I was looking for any -1's and didn't see any... and +3 after a week is sufficent ?
Perhaps the proposal could have been more clear. My understanding of the outcome was "releng retires these packages". I didn't mean to imply a ongoing commitment, but I suppose that might be a good idea.
I'll reopen for more discussion I guess...
Metadata Update from @kevin: - Issue status updated to: Open (was: Closed)
Metadata Update from @humaton: - Issue untagged with: pending announcement
The proposal explicitly said: "This retirement procedure shall be repeated as releng finds appropriate". Can somebody who has the privs merge the docs PR and then releng can run the procedure once and we can forget about this for a year or two?
The PR was merged. The ball is now in releng's court.
https://pagure.io/releng/issue/12629 tracks the implementation.
Metadata Update from @zbyszek: - Issue close_status updated to: Accepted - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.