.NET Life Cycle
Microsoft establishes and maintains the life-cycle support policy for .NET on Red Hat Enterprise Linux. This life cycle may differ from the Red Hat Enterprise Linux life cycle for certain SKUs.
Developers can use either the Long Term Support (LTS) releases or Standard Term Support (STS) releases. LTS releases are long term supported. STS releases bring the latest innovations and features. Both LTS and STS releases receive critical fixes.
LTS releases are supported for 3 years after the general availability date or 1 year after the general availability of a subsequent LTS release. STS releases are supported for 3 months after the general availability of a subsequent (STS or LTS) release.
.NET Release Life Cycle
Architecture Support
Red Hat .NET for 64-bit AMD and Intel (x86_64) (multiple versions, up to and including .NET 6.0) are available for RHEL 7.
Support for .NET on RHEL 7 ended on June 30, 2024.
Red Hat .NET for 64-bit AMD and Intel (x86_64) (multiple versions) are available for RHEL 8 and later
Red Hat .NET 6 and newer are available for Z (s390x), on RHEL 8 and later
Red Hat .NET 7 is available for IBM Power (ppc64le), on RHEL 8 and later
Red Hat .NET 6 and newer are available for 64-bit ARM (aarch64) on RHEL 8 and later
.NET Program Support
Red Hat will assist Red Hat Enterprise Linux users with the installation and runtime usage of .NET. Any other support of the .NET components is provided by Microsoft.
Red Hat customers can engage Red Hat Technical Support directly. If the Red Hat Support Engineer assigned to a case needs assistance from Microsoft, the Red Hat Support Engineer collaborates with Microsoft directly without any action required from the customer. Likewise on the Microsoft side, they have a process for directly collaborating with Red Hat Support Engineers.
The Red Hat Enterprise Linux developer subscriptions offered as a part of the Red Hat Developer Program are self-supported and intended for development purposes only; they are not intended for other purposes such as production environments; and may not address known security vulnerabilities.
