endoflife-date / endoflife.date

Informative site with EoL dates of everything
https://endoflife.date
MIT License
2.45k stars 751 forks source link

Red Hat Enterprise Linux #3318

Open neorus616 opened 1 year ago

neorus616 commented 1 year ago

Link to product page on endoflife.date

https://endoflife.date/rhel

Details of incorrect and correct details you have found

According to RHEL life cycle, they have EOL date for each minor version, and not for major only https://access.redhat.com/support/policy/updates/errata aka it should be checked for "8/9.X" version and not "8/9", as for example 9.1 is already EOL, because 9.2 is out already

What is the source website for the product and for its version information?

https://access.redhat.com/support/policy/updates/errata https://access.redhat.com/sites/default/files/images/337_rhel_9_life_cycle_updates_0423.png

captn3m0 commented 1 year ago

Isn't that implicit here? The page states:

You should be running one of the supported release numbers listed above in the rightmost column.

And as such, the only supported 9.x release is the one listed - 9.2.

Since the lifecycle and dates are set on a major version, it makes sense to showcase the data in the same way. Splitting it by minor versions would make the page too verbose.

noqcks commented 1 year ago

The Red Hat page is very confusing. Does this say that they only provide security fixes until there's a new minor version. As soon as there's a new minor version the previous minor version becomes EOL?

Under a Red Hat Enterprise Linux subscription, all available RHSAs and RHBAs are provided for the current active minor release until the availability of the next minor release. By contrast, Enhanced Extended Update Support for RHEL —for a specific minor release—an independent, extended stream of those Red Hat defined Critical and Importantix impact RHSAs and selected (at Red Hat discretion) Urgent Priority RHBAs that are available after that specific minor release and in parallel to subsequent minor releases.

I tend to agree @neorus616 that the page is incorrect here and that correct verbosity would be better than incorrect terseness. Additionally, I think the way it is now prevents any tool/API usage.

Poil commented 12 months ago

RedHat has EOL on minor version, some minor version have long term support RedHat guaranty ABI compatibility in a major version but between 2 minors versions you may have some "minor" breaking changes.

You can "pin" to a minor version Some software like SAP is only supported with a LTS minor version.

It makes sense to report minor version that are EOL on RedHat Enterprise.

TJuberg commented 1 week ago

Came here looking for this myself.

It would be tremendously helpful to be able to query the minor versions for RHEL given that numerous factors that can impact the different EOL dates that affect each even point release (and there can be exceptions to the even rule as was the case with 8.1 instead of 8.0)

Essentially each RHEL major/minor release has it's own set of 3 end of life dates. See RHEL 8 Planning Guide and RHEL 9 Planning Guide for example, with 9 introducing Enhanced Extended Update Support

Right now only 9.4, 8.10 and 7.9 are listed explicitly. However the following versions are still supported with EUS, EEUS or ELS

EEUS is a new extended lifecycle phase introduces with RHEL 9 and extends point release support equal to that of Update services for SAP which in pracrise meant that SAP could be ignored as a corner case before RHEL 9 for the majority of users/companies.

In addition Redhat 7 is listed as end of life, which is not really true. It has only reached end of maintenance support while still having years left of support and fixes for critical security/bug issues with ELS. RHEL 7 will not reach EOL until June 30, 2028 when ELS ends. Source

It would help tremendously if it was possible to query for these with an API. And while having the last possible EOL date for a point release, it would be nice if all of the lifecycle phases could make it in as I all too often need to refer to them and would love to be able to query them by API.

Edit: As an addendum, I have already had "fights" in regards to compliance and reviews where endoflife.date is pointed to as a source to prove that we are running end of life software when it is not the case. The same goes for Ubuntu where 16.04 is listed as eol, but at least it is shown as having extended support available. For RHEL it only shows 1 release for each major version at any given time. In fact, the term "end of life" is not even used by Ubuntu themselves in their lifecycle. Only End of support in their lifecycle overview.

I think the only way to list eol dates in a way that satisfies all purposes is to have two EOL dates listed. eol without paid addons, and eol with support. As long as you have support with fixes for security and critical issues the product cannot be classified as eol. And with the caveat that paid support only reflects support from the vendor themselves. Things get muddy if/when third parties like Suse Liberty Linux offering support and security fixes until 2028 for CentOS 7 gets thrown into the mix,

Edit2: Sour grapes to RedHat for managing to make it impossible to find all the information easily and spreading everything across numerous pages. https://access.redhat.com/articles/4038291 seems to be the best entrypoint I have come across so far which gives you good info on minor releases as well as linking to current support dates and life-cycle dates.