#50 [RFE] An EoL Policy for EPEL8 modules
Closed: Unable to Fix a year ago by tdawson. Opened 5 years ago by mprahl.

As we prepare for EPEL8 modules, could EPSCO come up with an EoL policy for modules? Can packagers maintain short-lived EPEL8 modules or must we maintain modules for the lifespan of RHEL8? If we can have short-lived EPEL8 modules, how do we declare the EoL? What is the minimum EoL?


How does the following proposal sound:

EPEL Package Lifetimes

All packages have a designed lifetime of one minor release of Red Hat Enterprise Linux or 1 year whichever comes first. Packages can have announced updates and removals when EPEL announces it is archiving the last minor release. Modules can have their lifetimes enforced with the fpdc tools when this is possible.

That sounds fine, but I think we also need to make sure and notify people about stuff thats nearing eol... perhaps a weekly report with all modules and their eol date so maintainers could extend them or users can know to switch.

I agree on that. I don't know how much work that will take to implement but we can put it on the must-list.

In the end, this wasn't able to be implemented.
Since we are retiring modules in EPEL8, I am closing this issue.

Metadata Update from @tdawson:
- Issue close_status updated to: Unable to Fix
- Issue status updated to: Closed (was: Open)

a year ago

Login to comment on this ticket.

Metadata