Switch to Standard Term Support (STS) releases - #7517
Conversation
dcwhittaker
left a comment
dcwhittaker
left a comment
There was a problem hiding this comment.
Thank for you for doing this - I think this is much clearer for folks to understand.
|
That's the hope, for sure. |
|
I'll merge this in a bit. I'm going to publish a breaking change announcement, first. |
|
We should coordinate. The support policies on dot.net should match. |
|
How about you be the one to merge this PR, @mairaw? |
|
I also need to update docs. I'll create a PR on that next week. We can merge that one coordinated with the website. |
|
Sounds good @richlander. I didn't have time last week to create the PR. |
|
Not a problem. We're not in a rush. I'll get the docs PR in place first. That should set the stage for getting the website updated. I inserted a mention of STS in the Preview 5 blog post, which you may have seen in draft. |
|
Good change. Too many folks thinking that LTS = Stable. |
|
what is the plan for dotnet install scripts? |
|
We probably need to do similar changes on docs /cc @adegeo |
|
@mairaw -- I already added STS on this page: https://docs.microsoft.com/dotnet/core/introduction#support. Perhaps we can just do this as a rolling thunder type thing and merge this PR now? |
Co-authored-by: Genevieve Warren <24882762+gewarren@users.noreply.github.com>
There was a problem hiding this comment.
I uncapitalized the support terms since they aren't product names or anything like that. From https://styleguides.azurewebsites.net/StyleGuide/Read?id=2696&topicid=25357:
"If it’s not a brand, product, service, or app it’s lowercase."
|
|
||
| [.NET 7](https://devblogs.microsoft.com/dotnet/announcing-dotnet-7-preview-2/) will be a [current release](../../release-policies.md) and will be supported for 18 months, from November 2022 to May 14, 2024. It is [supported by Microsoft](../../microsoft-support.md) on [multiple operating systems](supported-os.md). | ||
|
|
||
| [.NET 7](https://devblogs.microsoft.com/dotnet/announcing-dotnet-7-preview-4/) is an [STS release](../../release-policies.md) and will be supported for 18 months, from November 8th, 2022 to May 14th, 2024. It is [supported by Microsoft](../../microsoft-support.md) on [multiple operating systems](supported-os.md). |
There was a problem hiding this comment.
| [.NET 7](https://devblogs.microsoft.com/dotnet/announcing-dotnet-7-preview-4/) is an [STS release](../../release-policies.md) and will be supported for 18 months, from November 8th, 2022 to May 14th, 2024. It is [supported by Microsoft](../../microsoft-support.md) on [multiple operating systems](supported-os.md). | |
| [.NET 7](https://devblogs.microsoft.com/dotnet/announcing-dotnet-7-preview-4/) is a [Standard Support release](../../release-policies.md) and will be supported for 18 months, from November 8, 2022 to May 14, 2024. It is [supported by Microsoft](../../microsoft-support.md) on [multiple operating systems](supported-os.md). | |
There was a problem hiding this comment.
Note that Windows also does caps for LTSC -> https://learn.microsoft.com/en-us/windows/whats-new/ltsc/
| # .NET 7 - Supported OS versions | ||
|
|
||
| [.NET 7](README.md) [is supported](https://github.com/dotnet/core/blob/main/microsoft-support.md) on multiple operating systems per their [lifecycle policy](../../os-lifecycle-policy.md). | ||
| [.NET 7](README.md) is an [STS release](../../release-policies.md) and [is supported](../../microsoft-support.md) on multiple operating systems per their lifecycle policy. |
There was a problem hiding this comment.
| [.NET 7](README.md) is an [STS release](../../release-policies.md) and [is supported](../../microsoft-support.md) on multiple operating systems per their lifecycle policy. | |
| [.NET 7](README.md) is a [Standard Support release](../../release-policies.md) and [is supported](../../microsoft-support.md) on multiple operating systems per their lifecycle policy. |
| ## Release types | ||
|
|
||
| LTS and Current releases have many similarities. The .NET team follows the same software engineering and release processes for both release types, including for security, compatibility, and reliability. Both releases may contain major new features and breaking changes. The .NET team aspires to enable straightforward migration from one release to another (LTS or Current, in either direction), and has processes in place to achieve that intention. | ||
| Each .NET release is defined as either **Standard Support** or **Long Term Support (LTS)**, at the beginning of the release. |
There was a problem hiding this comment.
| Each .NET release is defined as either **Standard Support** or **Long Term Support (LTS)**, at the beginning of the release. | |
| Each .NET release is defined as either **Standard Support** or **Long Term Support (LTS)**, at the beginning of the release. |
| Note: **Standard** releases were previously called **Current**. | ||
|
|
||
| Improvements are released as "patches". Patch releases are cumulative. Patches are released on the Microsoft "Patch Tuesday" (second Tuesday of each month), however there is no guarantee that there will be a .NET release on any given Patch Tuesday. Patches are announced on the [.NET blog](https://devblogs.microsoft.com/dotnet/). A digest of monthly releases is published to [dotnet/announcements](https://github.com/dotnet/announcements/labels/Monthly-Update). | ||
| LTS and Standard releases differ only by support duration. The .NET team follows the same software engineering and release processes for both release types, including for security, compatibility, and reliability. Both releases may contain major new features and breaking changes. The .NET team aspires to enable straightforward migration from one release to another, independent of release type. |
There was a problem hiding this comment.
| LTS and Standard releases differ only by support duration. The .NET team follows the same software engineering and release processes for both release types, including for security, compatibility, and reliability. Both releases may contain major new features and breaking changes. The .NET team aspires to enable straightforward migration from one release to another, independent of release type. | |
| LTS and Standard Support releases differ only by support duration. The .NET team follows the same software engineering and release processes for both release types, including for security, compatibility, and reliability. Both releases may contain major new features and breaking changes. The .NET team aspires to enable straightforward migration from one release to another, independent of release type. |
|
|
||
| Functional improvements are typically very targeted, and may address the following: | ||
| * **Preview** releases are not supported but are offered for public testing and for the opportunity to give feedback. | ||
| * **Go-live** support enables users to deploy a pre-release build in production, and are supported by Microsoft. These are typically Release Candidate (RC) releases. |
There was a problem hiding this comment.
| * **Go-live** support enables users to deploy a pre-release build in production, and are supported by Microsoft. These are typically Release Candidate (RC) releases. | |
| * **Go-live** support enables users to deploy a pre-release build in production, and are supported by Microsoft. These are typically release candidate (RC) releases. |
|
I think standardizing on title case or all lowercase would be a question for @jamshedd and @richlander. Let me know the preference and I'll adjust accordingly on all PRs. It needs to be consistent. |
I think we need to keep this Long Term Support (LTS) and Standard Support with that capitalization in our content/website/etc. the one exception to this is the releases.json where the enums already use all lower case, so we'd keep that to be consistent with the rest of the file. |
I'll go with that, but it does go against the Cloud & AI style guide. Also if we lower-case "standard support" it becomes less of a confusion with ".NET Standard", which is always capitalized. |
Thanks for the pointer Genevieve. I don't think there's a real risk of anyone confusion .NET Standard (the target) and Standard Support (the support policy). I would stick with the capitalization as it exists. |
Co-authored-by: Genevieve Warren <24882762+gewarren@users.noreply.github.com>
| # .NET 6 - Supported OS versions | ||
|
|
||
| [.NET 6](README.md) [is supported](https://github.com/dotnet/core/blob/main/microsoft-support.md) on multiple operating systems per their [lifecycle policy](../../os-lifecycle-policy.md). | ||
| [.NET 6](README.md) is an [LTS release](../../release-policies.md) and [is supported](../../microsoft-support.md) on multiple operating systems per their lifecycle policy. |
There was a problem hiding this comment.
"per their lifecycle policy" is incorrect because it implies we follow the OS lifecycle (like Framework) which we don't. In reality we support the OS as long as the OS and .NET are both in support, whichever is shorter.
So I would recommend replacing this phrase with something like "per the OS support matrix defined for the release"
There was a problem hiding this comment.
I don't see it that way. The wording seems accurate and intuitive.
implies we follow the OS lifecycle (like Framework) which we don't
Almost no reader will come to this conclusion.
| * **Release Candidate** releases have a go-live support that enables users to deploy a pre-release build in production and are supported by Microsoft. | ||
| * **Active** support is provided for the majority of the period after a release is generally available (GA). Functional and security improvements will be provided, including support for new operating system versions. | ||
| * **Maintenance** support is provided for the last six months of support. Improvements are limited to security fixes. Support for new operating system versions will be provided on a best-effort basis. | ||
| * **End of support** or end-of-life (EOL) marks the point where a release is no longer supported. |
There was a problem hiding this comment.
| * **End of support** or end-of-life (EOL) marks the point where a release is no longer supported. | |
| * **End of support** or end-of-life (EOL) marks the point where a release no longer receives servicing updates and is no longer supported. |
There was a problem hiding this comment.
I don't see that this addition is necessary. It is fully implied and called out in full detail in a later section.
| Patches are announced in [release notes](release-notes/README.md), on the [.NET blog](https://devblogs.microsoft.com/dotnet/category/maintenance-and-updates/), and [dotnet/announcements](https://github.com/dotnet/announcements/labels/Monthly-Update). | ||
|
|
||
| The maintenance support period is the final 6 months of support for any release (Current or LTS). After the maintenance period ends, the release is out of support. | ||
| Breaking changes are not accepted during servicing, except (in the very rare case) to resolve critical issues, such as a security vulnerability. |
There was a problem hiding this comment.
| Breaking changes are not accepted during servicing, except (in the very rare case) to resolve critical issues, such as a security vulnerability. | |
| Breaking changes are not accepted during servicing, except (in the very rare case) to resolve critical issues, such as a security vulnerability. Breaking changes are documented. |
There was a problem hiding this comment.
This doesn't make much sense.
"We don't make breaking changes"
"Breaking changes are documented".
|
|
||
| Functional improvements are typically very targeted, and may address the following: | ||
| * **Preview** releases are not supported but are offered for public testing and for the opportunity to give feedback. | ||
| * **Release Candidate** releases have a go-live support that enables users to deploy a pre-release build in production and are supported by Microsoft. |
There was a problem hiding this comment.
"Release Candidate" should be changed to "Go-Live"
| * **Release Candidate** releases have a go-live support that enables users to deploy a pre-release build in production and are supported by Microsoft. | ||
| * **Active** support is provided for the majority of the period after a release is generally available (GA). Functional and security improvements will be provided, including support for new operating system versions. | ||
| * **Maintenance** support is provided for the last six months of support. Improvements are limited to security fixes. Support for new operating system versions will be provided on a best-effort basis. | ||
| * **End of support** or end-of-life (EOL) marks the point where a release is no longer supported. |
There was a problem hiding this comment.
"End of support" should be "End of life"
Co-authored-by: Jamshed Damkewala <jamshedd@users.noreply.github.com>
8 participants
The "Current" term is switching to "Standard Term Support (STS)". It nicely and intuitively contrasts with "Long Term Support (LTS)". Nothing else is changing (beyond the name).
For more information, see: https://github.com/dotnet/core/blob/main/release-policies.md
Relates to: