.NET Core 2.0 has reached end of life
leecow opened this issue · 0 comments
.NET Core 2.0 reached end of life on October 1, 2018. This means .NET Core 2.0 is no longer supported and updates will no longer be provided. We recommend moving to .NET Core 2.1, our long term support (LTS) release.
Discussion
Please share you thoughts on this change and see what others are saying at:
Lifecycle Context
.NET Core releases belong to one of two support lifecycles: long term support (LTS) and Current. LTS releases are stable release which receive critical updates and are supported for at least three years. Current releases can include new features that may undergo future change based on feedback. Current releases are supported for three months after the subsequent .NET Core major or minor release. Both LTS and Current releases receive critical fixes throughout their lifecycle, for security, reliability, or to add support for new operating system versions. You must stay up-to-date with the latest patches to qualify for support.
.NET Core 2.0 Lifecycle
.NET Core 2.0 was released in August 2017 as a Current release. Per the lifecycle policy, Current releases reach end of life 3 months after a subsequent release (Current or LTS). .NET Core 2.1 released May 2018 and began the end of life countdown for .NET Core 2.0. The 3 month maintenance period for .NET Core 2.0 was scheduled to end August 2018 but was extended to October to allow time to address an issue some customers were experiencing while migrating to .NET Core 2.1.
.NET Core 2.0 Downloads
.NET Core 2.0 installers, zips and tar.gzs will remain available, but unsupported. This includes existing releases available on Linux package feeds. Previous versions, including 2.0, will be accessible through the .NET Downloads page.
.NET Core 2.0 Docker Images
.NET Core 2.0 will be removed from the .NET and ASP.NET Docker repo READMEs, however the existing images remain available in those repos.
Policy Information
Additional lifecycle and support details and background can be seen in the following: