#4 Decide on criteria to unretire packages.
Closed: Fixed a year ago by carlwgeorge. Opened 8 years ago by till.

https://fedoraproject.org/wiki/Orphaned_package_that_need_new_maintainers#Claiming_Ownership_of_a_Retired_Package defines the criteria to unretire packages in Fedora and in EPEL if the package is still active in Fedora. However there is now a request to unretire a package that is also retired in all branches for more than two weeks (at least in pkgdb):
https://lists.fedoraproject.org/pipermail/epel-devel/2014-September/010212.html

Therefore the question is, whether a re-review is required. IMHO it does not make much sense for EPEL, since there should be no guideline changes that require adjusting the EPEL SPEC files. Nevertheless, I would like to get a consensus on this.


I agree that reviews for such things do not make sense for EPEL. If we have them, I wonder if there is an expedited way of doing so?

Update to ticket. We did not have a full body of committee members on 2014-10-03 meeting so are going to put this to the next meeting.

Second note. We are going to look at reviewing xerces-c using old method so that broken deps can be dealt with.

Agreed by bstinson, Evolution, smooge, nirik

a) smooge volunteers to be a reviewer who will do reviews of needed packages on Friday afternoons after I have been retrained.
b) We have a bug-killing day once a month where CentOS packagers help
c) We expect all packages that have been removed from the collection over 14 days to be re-reviewed. [This is to match upstream FESCO policy]

Replying to [comment:3 smooge]:

Agreed by bstinson, Evolution, smooge, nirik

a) smooge volunteers to be a reviewer who will do reviews of needed packages on Friday afternoons after I have been retrained.
b) We have a bug-killing day once a month where CentOS packagers help
c) We expect all packages that have been removed from the collection over 14 days to be re-reviewed. [This is to match upstream FESCO policy]

Is this now documented somewhere? Is there someone to coordinate the bug-killing day? I guess there should be a wiki page about the bug-killing day some planning with announcements about when it will be.

And for others, that might be interested, the relevant meeting log is here:
http://meetbot.fedoraproject.org/epel/2014-10-31/epel.2014-10-31-20.01.html

Metadata Update from @smooge:
- Issue assigned to smooge

5 years ago

We shall look at doing a bug-killing day after FLOCK 2017 in Cape Code. I would like to work out who wants to help and what they can work on as part of https://flock2017.sched.com/event/Bm8q/epel-for-the-future

Metadata Update from @smooge:
- Issue close_status updated to: None

5 years ago

Metadata Update from @smooge:
- Assignee reset

2 years ago

Since this ticket was opened, we have migrated away from pkgdb. Package retirement works differently in pagure now. Packages are retired on a per branch basis, so a package being retired in rawhide doesn't affect epel branches. I'm going to close this out, but if I'm missing something or we need additional clarification in the guidelines feel free to re-open.

Metadata Update from @carlwgeorge:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

a year ago

Login to comment on this ticket.

Metadata