#196 Add initial policy for end of life EPEL releases
Merged 2 years ago by tdawson. Opened 2 years ago by kevin.

@@ -361,3 +361,14 @@ 

  

  No re-review is required to unretire an EPEL branch if the package is

  still in Fedora.

+ 

+ [[policy_for_end_of_life_releases]]

+ == Policy for End of Life releases

+ 

+ When a RHEL release reaches the end of the Maintenance Support phase

+ https://access.redhat.com/support/policy/updates/errata#Life_Cycle_Dates[ RHEL life cycle ] 

+ , The corresponding EPEL release also goes End of Life. 

+ On the day Maintenance Support ends for the RHEL release, koji build targets are removed and

+ it is no longer possible to build or distribute new EPEL packages.

+ A short time after that, the now end of life EPEL repository is moved to

+ archives and mirrormanager is adjusted to serve that repository from archives.

Here's an inital cut of this. Changes welcome.

Signed-off-by: Kevin Fenzi kevin@scrye.com

LGTM
Sounds like what we decided on in last weeks meeting.

Can we be more specific than "End of Life"? I believe most of us understand what that means, but for the policy I think we should explicitly say "When a RHEL release reaches the end of the Maintenance Support phase" with a link to https://access.redhat.com/support/policy/updates/errata#Life_Cycle_Dates.

s/day of End of Life/End of Life date/

rebased onto 1f0b87f

2 years ago

New version pushed. ;)

I like the changes.

Just had a thought, should we also add another sentence saying with the equivalent information about EPEL Next? It could reference the end of the Active Support phase.

Although I like Carl's idea, let's get this pull request merged and start a new one for that.

I have verified that this builds and the link is correct.

Pull-Request has been merged by tdawson

2 years ago
Metadata