.NET Core Life Cycle

Microsoft establishes and maintains the life-cycle support policy for .NET Core 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 Current releases.

LTS releases are normally major releases (for example, 1.0) and only receive critical fixes. Current releases are minor releases (for example, 1.1.x) and receive the same fixes. Releases will be revised when compatible innovations and features are available. LTS releases are supported for 3 years after the general availability date or 1 year after the general availability of a subsequent LTS release.

According to Microsoft, Current releases are supported within the same 3-year window as the parent LTS release. They are supported for 3 months after the general availability of a subsequent Current release and 1 year after the general availability of a subsequent LTS release. See Microsoft's .NET Core Support Policy for more details.

.NET Core for Red Hat Enterprise Linux Life Cycle

Version Support Level General Availability End of Life
1.0 Maintenance June 2016 June 27, 2019
1.1 Maintenance November 2016 June 27, 2019
2.0 EOL August 2017 October 1, 2018
2.1 LTS June 2018 April 2019
2.2 Current December 2018 3 months after a subsequent Current or LTS release

.NET Core Program Support

Red Hat will assist Red Hat Enterprise Linux users with the installation and runtime usage of .NET Core. Any other support of the .NET Core 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 the Red Hat Developer Program are self-supported and intended for development purposes only; are not intended for other purposes, such as production environments; and may not address known security vulnerabilities.