Give some information about RHEL ELS

[maxenced]

RedHat provides some Extended life support add-on which provides updates for a subset of packages for some extra duration after EOL. Ref : https://access.redhat.com/support/policy/updates/errata#Life_Cycle_Dates

Is there any chance to provide information about this (especially in api/json file) ? Not sure what would be the best between having an extra cycle like "RHEL 6 ELS", or just some extra fields in the default cycle ?

[welcome[bot]]

Thanks for opening your first issue here! Be sure to follow the issue template!

[usta]

@BiNZGi @captn3m0

[BiNZGi]

As I saw the ELS is an additional service which must be paid via subscription. We are having a similar discussion in the Java topic. But in this case it is a bit different because only Red Hat provides this service.

The RHEL page is not that crowded and from my side it would be a good addition for the users of our page. If we agree to support the ELS details I would add an extra cycle as proposed.

[BiNZGi]

Related to discussion #535

[captn3m0]

The only (minor) concern I have is that every RHEL release is currently supported with ELS, so it's not very meaningful (could be covered in the text as well for now - "All RHEL releases are currently supported with a paid ELS subscription").

[maxenced]

Mhh, I don't understand it that way. As per https://access.redhat.com/support/policy/updates/errata#Life_Cycle_Dates , only RHEL 6,7,8 are still covered by an active ELS support. RHEL 5 ELS ended in 202 and 4 in 2017 (but the Extended life phase ends column is a bit strange)

[captn3m0]

Yeah, was confused with that, looks like we shouldn't be tracking Extended Life Phase, since it doesn't cover any fixes, just technical support.

So +1 to adding ELS as a separate row for the supported releases.

For versions of products in the Extended Life Phase, Red Hat will provide limited ongoing technical support. No bug fixes, security fixes, hardware enablement or root-cause analysis will be available during this phase, and support will be provided on existing installations only.

[Evernow]

So +1 to adding ELS as a separate row for the supported releases.

Is this currently possible?

[captn3m0]

Yeah, just an extra repeated row with ELS in the releaseCycle field.

[Evernow]

Yeah, just an extra repeated row with ELS in the releaseCycle field.

Can you clarify? Would it be like this:

  - releaseCycle: "RHEL 8"
    release: 2019-05-01
    support: 2024-05-31
    eol: 2029-05-31
    ELS: 2029-12-31 # Example
    latest: "8.5"

[Evernow]

Looking at further, I believe you meant having a completely different releaseCycle with ELS in the name? Personally believe that is not ideal. Just by looking at the Windows entry it can result in a mess to put it mildly.

Unfortunately I'm not familiar with HTML, Rudy or netlify to see how easy it would be to have an additional column for dates, but this would be highly useful especially for entries such as Ubuntu, RHEL, Windows, and potentially others that have more than just two support structures.

[captn3m0]

Looking at further, I believe you meant having a completely different releaseCycle with ELS in the name

Yes, that was the idea. As it stands, the code does a lot of templating logic, along with calculations to render the tables and it's not easy to easily add more columns. Let's go for the new release cycle row for now?

Can you provide a table that you think will work for our site? (With ELS as a column?). Will track it in a separate issue on how we can do more columns more easily (we only have discontinued right now, and it's not very easy to add more).

[Evernow]

Is this covered with https://github.com/endoflife-date/endoflife.date/pull/1254 ?

[marcwrobel]

Should be covered now by the "Extended Life Cycle Support" on https://endoflife.date/rhel.

Will be available from the API once #2080 is completed and merged.

[marcwrobel]

Closing this issue because it should be OK now. Do not hesitate to reopen if necessary.