- Which version of Red Hat Enterprise Linux is best for me?
- 1 Maximizing your life cycle
- 2 Application supportability
- 3 Long-term stability
- 4 Seeking innovation
- 5 Extending hardware retirement
- 6 Kernel functionality
- Red Hat Enterprise Linux Release Dates
- Red Hat Enterprise Linux 9
- Red Hat Enterprise Linux 8
- Red Hat Enterprise Linux 7
- Red Hat Enterprise Linux 6
- Red Hat Enterprise Linux 5
- Red Hat Enterprise Linux 4
- Red Hat Enterprise Linux 3
- Red Hat Enterprise Linux 2.1
Which version of Red Hat Enterprise Linux is best for me?
It is time to upgrade your Red Hat® Enterprise Linux® operating system. Are you wondering which version is right for you? Your subscription allows you the freedom to choose whichever available version best suits your needs. With its new predictable release cadence and more supported versions available, knowing the key differences between Red Hat Enterprise Linux 8 and Red Hat Enterprise Linux 9 will help you decide which version is best for you. While the next closest version may seem like the obvious choice, an even later version might actually make more sense for you.
1 Maximizing your life cycle
The decision to upgrade a system, instead of migrating to a new host, typically stems from needing to manage the availability and life cycle of an existing application, whether it be to upgrade underlying components for better performance or to extend support of a critical workload. Either way, moving to an operating system (OS) currently in the Full Support phase from the Maintenance or even Extended Life phase means more updates will be available for a longer period of time.
For example, with Red Hat Enterprise Linux 7 Server currently in Maintenance phase 2, Red Hat Enterprise Linux 8 remains in Full Support until May 2024, with Red Hat Enterprise Linux 9 in Full Support until May of 2027. The Red Hat Enterprise Linux Life Cycle page lays out an easy-to-use map and a table for simple comparisons.
Full Support means that new features, new streams, and new hardware are being added in addition to fixes and updates. Moving to Red Hat Enterprise Linux 9 means having a longer period of active OS development, with an overall longer supported life cycle.
At the time of a new major release of Red Hat Enterprise Linux, the technology gap between the new version and the previous version is fairly small, but as time goes on backporting features into the previous version becomes more difficult. This leads to more divergence over time, even during the Full Support phase.
Having the latest combination of your applications and hardware on the latest version of the OS maximizes the available support life cycle.
2 Application supportability
Making the choice to upgrade often involves commercial applications from enterprise independent software vendors (ISVs). Upgrading the operating system while maintaining the same version of applications is often done to promote stability and supportability of those enterprise applications. Understanding which versions of Red Hat Enterprise Linux are supported by those ISVs can guide your choices.
Red Hat’s extensive partner network validates and certifies their software components against various versions of Red Hat Enterprise Linux. As partners, we are also working to provide updated packages and libraries that match what we are each looking for long term. This means that ISV certifications are often tied to specific major versions of Red Hat Enterprise Linux.
If an ISV partner is looking for newer software components to build against, or newer hardware features to take advantage of, Red Hat Enterprise Linux 9 may be the right choice.
Considering the change over time between versions under full support, your current commercial application may still be under testing or even development at the general availability of a new release of Red Hat Enterprise Linux.
3 Long-term stability
For applications developed in-house, replatforming selected components could mean big investments with little-to-no appreciable benefits. Existing applications built around specific versions of common development tools and components could be disrupted during an upgrade, or even during a migration.
The availability of application streams in Red Hat Enterprise Linux 8 and 9 provide multiple versions of common components, meaning it is easier to provide a stable environment for existing applications while still taking advantage of newer operating environments and management tooling.
Red Hat Enterprise Linux 8 provides older versions of components as well as new components released during the life cycle, which can provide a way to transition smoothly between component versions.
4 Seeking innovation
Teams are often looking to update or rearchitect existing applications to take advantage of the latest technology choices. Upgrading operating systems also means access to newer sets of operational and development tools and components. Access to the latest technologies and tools allows teams to deliver new projects faster and address refactoring and new patterns easier.
With multiple versions of components containing application streams and later versions of supported operating systems, current environments can take big leaps forward while still maintaining some compatibility.
Red Hat Enterprise Linux 9 will continue to support newer technologies as new versions are released providing users with greater choice.
5 Extending hardware retirement
Sometimes the goals for upgrades are above the operating system but rely on existing infrastructure. Getting the most out of datacenter investments while updating software capabilities can make sense in many cases.
Like the ISV ecosystem, Red Hat’s network of hardware partners supports a wide range of devices. Between major releases and in conjunction with those partners, certain devices may no longer be supported. Choosing the right version of Red Hat Enterprise Linux can provide an updated platform for software while still maintaining support for previous generations of hardware.
Major releases are typically a deprecation boundary for older hardware. Older hardware that is no longer supported by the manufacturer may not be available in Red Hat Enterprise Linux 9.
6 Kernel functionality
The choice to upgrade instead of rebuild sometimes comes down to the core features delivered within Red Hat Enterprise Linux. Access to the latest updates to, and capabilities of, packages may require the move to a later version of the OS. While features and security fixes are often backported, major versions often present newer baselines for packages that include changes that cannot be provided by a backport.
For example, the Red Hat Enterprise Linux 7 kernel is based on the upstream 3.10 version, while Red Hat Enterprise Linux 8 is based on the upstream 4.18, and Red Hat Enterprise Linux 9 on upstream 5.14. Feature and security updates from later versions may be backported into the earlier version, but large structural changes would wait until a new major version of Red Hat Enterprise Linux.
Backporting only goes so far—eventually you need new capabilities that cannot be handled using streams.
Red Hat Enterprise Linux Release Dates
The tables below list the major and minor Red Hat Enterprise Linux updates, their release dates, and the kernel versions that shipped with them.
Red Hat does not generally disclose future release schedules.
Refer to the Red Hat Enterprise Linux Life Cycle Policy for details on the life cycle of Red Hat Enterprise Linux releases.
To find your Red Hat Enterprise Linux release please:
To find your kernel version please:
Red Hat Enterprise Linux 9
| Release | General Availability Date | redhat-release Errata Date* | Kernel Version |
|---|---|---|---|
| RHEL 9.2 | 2023-05-10 | 2023-05-09 RHBA-2023:2455 | 5.14.0-284.11.1.el9_2 |
| RHEL 9.1 | 2022-11-15 | 2022-11-15 RHBA-2022:8264 | 5.14.0-162.6.1.el9_1 |
| RHEL 9.0 | 2022-05-17 | 2022-05-17 RHBA-2022:3893 | 5.14.0-70.13.1.el9_0 |
Red Hat Enterprise Linux 8
| Release | General Availability Date | redhat-release Errata Date* | Kernel Version |
|---|---|---|---|
| RHEL 8.8 | 2023-05-16 | 2023-05-16 RHBA-2023:2946 | 4.18.0-477.10.1.el8_8 |
| RHEL 8.7 | 2022-11-09 | 2022-11-09 RHBA-2022:7677 | 4.18.0-425.3.1 |
| RHEL 8.6 | 2022-05-10 | 2022-05-10 RHBA-2022:1984 | 4.18.0-372.9.1 |
| RHEL 8.5 | 2021-11-09 | 2021-11-09 RHBA-2021:4352 | 4.18.0-348 |
| RHEL 8.4 | 2021-05-18 | 2021-05-18 RHBA-2021:1569 | 4.18.0-305 |
| RHEL 8.3 | 2020-11-03 | 2020-11-03 RHBA-2020:4495 | 4.18.0-240 |
| RHEL 8.2 | 2020-04-28 | 2020-04-28 RHBA-2020:1758 | 4.18.0-193 |
| RHEL 8.1 | 2019-11-05 | 2019-11-05 RHBA-2019:3543 | 4.18.0-147 |
| RHEL 8 | 2019-05-07 | — | 4.18.0-80 |
Codename: Ootpa (is based on Fedora 28, upstream Linux kernel 4.18, systemd 239, and GNOME 3.28.)
Red Hat Enterprise Linux 7
| Release | General Availability Date | redhat-release Errata Date* | Kernel Version |
|---|---|---|---|
| RHEL 7.9 | 2020-09-29 | 2020-09-29 RHBA-2020:3849 | 3.10.0-1160 |
| RHEL 7.8 | 2020-03-31 | 2020-03-31 RHBA-2020:1033 | 3.10.0-1127 |
| RHEL 7.7 | 2019-08-06 | 2019-08-06 RHBA-2019:2351 | 3.10.0-1062 |
| RHEL 7.6 | 2018-10-30 | 2018-10-30 RHBA-2018:3014 | 3.10.0-957 |
| RHEL 7.5 | 2018-04-10 | 2018-04-10 RHEA-2018:0700 | 3.10.0-862 |
| RHEL 7.4 | 2017-07-31 | 2017-07-31 RHBA-2017:1850 | 3.10.0-693 |
| RHEL 7.3 | 2016-11-03 | 2016-11-03 RHEA-2016:2143 | 3.10.0-514 |
| RHEL 7.2 | 2015-11-19 | 2015-11-19 RHEA-2015:2107 | 3.10.0-327 |
| RHEL 7.1 | 2015-03-05 | 2015-03-05 RHEA-2015:0524 | 3.10.0-229 |
| RHEL 7.0 GA | 2014-06-09 | — | 3.10.0-123 |
| RHEL 7.0 Beta | 2013-12-11 | — | 3.10.0-54.0.1 |
Codename: Maipo (based on a mix of Fedora 19, Fedora 20, and several modifications)
Red Hat Enterprise Linux 6
| Release | General Availability Date | redhat-release Errata Date* | Kernel Version |
|---|---|---|---|
| RHEL 6.10 | 2018-06-19 | 2018-06-19 RHBA-2018:1856 | 2.6.32-754 |
| RHEL 6.9 | 2017-03-21 | 2017-03-21 RHBA-2017:0723 | 2.6.32-696 |
| RHEL 6.8 | 2016-05-10 | 2016-05-10 RHBA-2016:0976 | 2.6.32-642 |
| RHEL 6.7 | 2015-07-22 | 2015-07-22 RHBA-2015:1260 | 2.6.32-573 |
| RHEL 6.6 | 2014-10-14 | 2014-10-13 RHBA-2014:1405 | 2.6.32-504 |
| RHEL 6.5 | 2013-11-21 | 2013-11-20 RHEA-2013:1546 | 2.6.32-431 |
| RHEL 6.4 | 2013-02-21 | 2013-02-21 RHEA-2013:0379 | 2.6.32-358 |
| RHEL 6.3 | 2012-06-20 | 2012-06-19 RHEA-2012:0971 | 2.6.32-279 |
| RHEL 6.2 | 2011-12-06 | 2011-12-06 RHEA-2011:1743 | 2.6.32-220 |
| RHEL 6.1 | 2011-05-19 | 2011-05-19 RHEA-2011:0540 | 2.6.32-131.0.15 |
| RHEL 6.0 | 2010-11-09 | — | 2.6.32-71 |
Codename: Santiago (based on a mix of Fedora 12, Fedora 13, and several modifications)
Red Hat Enterprise Linux 5
| Release | General Availability Date | redhat-release Errata Date* | Kernel Version |
|---|---|---|---|
| RHEL 5.11 | 2014-09-16 | 2014-09-16 RHEA-2014-1238 | 2.6.18-398 |
| RHEL 5.10 | 2013-10-01 | 2013-09-30 RHEA-2013-1311 | 2.6.18-371 |
| RHEL 5.9 | 2013-01-07 | 2013-01-07 RHEA-2013-0021 | 2.6.18-348 |
| RHEL 5.8 | 2012-02-20 | 2012-02-20 RHEA-2012:0315 | 2.6.18-308 |
| RHEL 5.7 | 2011-07-21 | 2011-07-20 RHEA-2011:0977 | 2.6.18-274 |
| RHEL 5.6 | 2011-01-13 | 2011-01-12 RHEA-2011:0020 | 2.6.18-238 |
| RHEL 5.5 | 2010-03-30 | 2010-03-30 RHEA-2010:0207 | 2.6.18-194 |
| RHEL 5.4 | 2009-09-02 | 2009-09-02 RHEA-2009:1400 | 2.6.18-164 |
| RHEL 5.3 | 2009-01-20 | 2009-01-20 RHEA-2009:0133 | 2.6.18-128 |
| RHEL 5.2 | 2008-05-21 | 2008-05-20 RHEA-2008:0436 | 2.6.18-92 |
| RHEL 5. 1 | 2007-11-07 | 2007-11-07 RHEA-2007:0854 | 2.6.18-53 |
| RHEL 5.0 | 2007-03-15 | — | 2.6.18-8 |
Codename: Tikanga (based on Fedora Core 6)
Red Hat Enterprise Linux 4
| Release/Update | General Availability Date | redhat-release Errata Date* | Kernel Version |
|---|---|---|---|
| RHEL 4 Update 9 | 2011-02-16 | 2011-02-16 RHEA-2011:0251 | 2.6.9-100 |
| RHEL 4 Update 8 | 2009-05-19 | 2009-05-18 RHEA-2009:1002 | 2.6.9-89 |
| RHEL 4 Update 7 | 2008-07-29 | 2008-07-24 RHEA-2008:0769 | 2.6.9-78 |
| RHEL 4 Update 6 | 2007-11-15 | 2007-11-15 RHBA-2007:0897 | 2.6.9-67 |
| RHEL 4 Update 5 | 2007-05-01 | 2007-04-27 RHBA-2007:0196 | 2.6.9-55 |
| RHEL 4 Update 4 | 2006-08-10 | 2006-08-10 RHBA-2006:0601 | 2.6.9-42 |
| RHEL 4 Update 3 | 2006-03-12 | 2006-03-07 RHBA-2006:0149 | 2.6.9-34 |
| RHEL 4 Update 2 | 2005-10-05 | 2005-10-05 RHEA-2005:786 | 2.6.9-22 |
| RHEL 4 Update 1 | 2005-06-08 | 2005-06-08 RHEA-2005:318 | 2.6.9-11 |
| RHEL 4 GA | 2005-02-15 | — | 2.6.9-5 |
Codename: Nahant (based on Fedora Core 3)
Red Hat Enterprise Linux 3
| Release/Update | General Availability Date | Kernel Version |
|---|---|---|
| RHEL 3 Update 9 | 2007-06-20 | 2.4.21-50 |
| RHEL 3 Update 8 | 2006-07-20 | 2.4.21-47 |
| RHEL 3 Update 7 | 2006-03-17 | 2.4.21-40 |
| RHEL 3 Update 6 | 2005-09-28 | 2.4.21-37 |
| RHEL 3 Update 5 | 2005-05-18 | 2.4.21-32 |
| RHEL 3 Update 4 | 2004-12-12 | 2.4.21-27 |
| RHEL 3 Update 3 | 2004-09-03 | 2.4.21-20 |
| RHEL 3 Update 2 | 2004-05-12 | 2.4.21-15 |
| RHEL 3 Update 1 | 2004-01-16 | 2.4.21-9 |
| RHEL 3 GA | 2003-10-22 | 2.4.21-4 |
Codename: Taroon (based on Red Hat Linux 9)
Red Hat Enterprise Linux 2.1
| Release/Update | General Availability Date | Kernel Version |
|---|---|---|
| RHEL 2.1 Update 7 | 2005-04-28 | — |
| RHEL 2.1 Update 6 | 2004-12-13 | 2.4.9-e.57 |
| RHEL 2.1 Update 5 | 2004-08-18 | 2.4.9-e.49 |
| RHEL 2.1 Update 4 | 2004-04-21 | 2.4.9-e.40 |
| RHEL 2.1 Update 3 | 2004-12-19 | 2.4.9-e.34 |
| RHEL 2.1 Update 2 | 2003-03-29 | 2.4.9-e.24 |
| RHEL 2.1 Update 1 | 2003-02-14 | 2.4.9-e.12 |
| RHEL 2.1 GA | 2002-03-23 | 2.4.9-e.3 |
Codename: Pensacola (AS) / Panama (ES) (based on Red Hat Linux 7.2)
* Helpful when cloning channels in Satellite for a minor version plus all errata prior to the next minor release using spacewalk-clone-by-date or the webUI.