epel

#190 Keep everything for 30 days after EOL
Closed: Fixed by carlwgeorge. Opened by tdawson.

Closed: Fixed
Reopen Issue

Centos is proposing that they keep their buildroot and infrastructure around for 30 days after EOL of a RHEL release. They have asked if EPEL would mind doing the same.

EPEL currently does not have an official number of days that we keep everything after a release goes EOL. It has always been whenever someone from release-engineering has the time.

I propose that we make it official that we keep everything for at least 30 days after EOL of a RHEL release.

The main reason why CentOS is proposing a 30 day delay is for their SIG's. It is possible for Red Hat to release an update the last weeks of a release. The SIG's would like a reasonable amount of time to get one final build in before everything goes to the archives.

If we also match CentOS's 30 day period for that, it would allow the CentOS SIG's to continue to use the normal EPEL infrastructure. This would allow them to have their extra 30 days without having to reconfigure their settings for one final build.

EPEL might also have some packages that people want to get a final build in before things go into archives.

It would also give EPEL users a bit of a buffer before things go away.

Metadata Update from @tdawson:
- Issue tagged with: meeting

I am confused by this request.. Fedora Infra doesn't delete EPEL content but move it to archives. We have mirrormanager then point to archives. If you had a CentOS 6 system you can still get EPEL packages from the 2-3 mirrors which have /pub/archives.

In this case, the sig doesn't have to reconfigure anything unless they have hard coded a baseurl to point to dl.fedoraproject.org/pub/epel/{7,8,9}/

After discussion in this weeks EPEL Steering Committee meeting, the following decisions were made.

  • The current EPEL policy of shutting down and EPEL release as soon as the RHEL release is EOL will continue. As someone put it "updates are cut off EOD on EOL day for RHEL".
    This means the build tags and targets will be removed. The content will be put into archives. As smooge said above, this means that the content will still be available normally through the mirrors.

  • The current wording in the documentation will be updated to state this, so there isn't any confusion.

Metadata Update from @tdawson:
- Issue untagged with: meeting

https://pagure.io/epel/pull-request/196

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

This issue has been migrated to Fedora Forge:
https://forge.fedoraproject.org/epel/steering/issues/190

Please continue any further discussion there.
Metadata
None
None
None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.