Create an "orphaning" process #205
Labels
No labels
back-burner
blocked
Closed As
Approved
Closed As
Cant Fix
Closed As
Deferred
Closed As
Duplicate
Closed As
Fixed
Closed As
Nothing to do
Closed As
Rejected
Closed As
Unable to fix
Closed As
Won't fix
epel-packagers-sig
errata
high-gain
high-trouble
low-gain
low-trouble
medium-gain
medium-trouble
meeting
monit
qa
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
epel/steering#205
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Fedora has a nice orphaning process. If a package maintainer decided they don't want to maintain a Fedora package anymore, they mark the package "Orphan" and give a reason. The package then goes through an automated process where emails go out, and others can take the orphaned package. After some time, if nobody has taken the package, the package is retired.
It would be nice to have something similar for EPEL packages.