Switch to Standard Term Support (STS) releases #7517

richlander · 2022-06-04T20:14:42Z

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:

dcwhittaker

Thank for you for doing this - I think this is much clearer for folks to understand.

richlander · 2022-06-06T15:35:15Z

That's the hope, for sure.

richlander · 2022-06-06T15:35:40Z

I'll merge this in a bit. I'm going to publish a breaking change announcement, first.

mairaw · 2022-06-06T17:16:51Z

We should coordinate. The support policies on dot.net should match.

richlander · 2022-06-06T17:29:24Z

How about you be the one to merge this PR, @mairaw?

richlander · 2022-06-10T21:23:56Z

I also need to update docs. I'll create a PR on that next week. We can merge that one coordinated with the website.

mairaw · 2022-06-12T18:33:49Z

Sounds good @richlander. I didn't have time last week to create the PR.

richlander · 2022-06-12T18:44:33Z

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.

leo-costa · 2022-06-14T21:48:27Z

Good change. Too many folks thinking that LTS = Stable.

mairaw · 2022-06-24T19:26:38Z

what is the plan for dotnet install scripts?
/cc @YuliiaKovalova

mairaw · 2022-06-24T21:02:26Z

We probably need to do similar changes on docs /cc @adegeo

richlander · 2022-06-30T17:41:07Z

@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?

release-policies.md

Co-authored-by: Genevieve Warren <[email protected]>

gewarren

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."

gewarren · 2022-10-14T01:08:02Z

release-notes/7.0/README.md


-[.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).


Suggested change

[.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).

Note that Windows also does caps for LTSC -> https://learn.microsoft.com/en-us/windows/whats-new/ltsc/

They are wrong too 😂

gewarren · 2022-10-14T01:08:13Z

release-notes/7.0/supported-os.md

 # .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.


Suggested change

[.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.

gewarren · 2022-10-14T01:09:00Z

release-policies.md

+## 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.


Suggested change

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.

gewarren · 2022-10-14T01:09:20Z

release-policies.md

+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.


Suggested change

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.

gewarren · 2022-10-14T01:10:08Z

release-policies.md


-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.


Suggested change

* **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.

release-policies.md

releases.md

mairaw · 2022-10-14T02:05:07Z

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.

jamshedd · 2022-10-14T02:11:54Z

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.

gewarren · 2022-10-14T02:25:54Z

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.

mairaw · 2022-10-14T02:32:21Z

Thanks for sharing that guidance @gewarren. We can standardize on lowercase across all materials. We just need to do a pass to ensure is all consistent. But I'll give the final word to @jamshedd.

jamshedd · 2022-10-17T16:23:53Z

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 <[email protected]>

jamshedd · 2022-10-20T01:35:55Z

release-notes/6.0/supported-os.md

 # .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.


"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"

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.

jamshedd · 2022-10-20T01:38:02Z

release-policies.md

+* **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.


Suggested change

* **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.

I don't see that this addition is necessary. It is fully implied and called out in full detail in a later section.

jamshedd · 2022-10-20T01:39:38Z

release-policies.md

+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.


Suggested change

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.

This doesn't make much sense.

"We don't make breaking changes"

"Breaking changes are documented".

release-policies.md

leecow · 2022-10-25T20:44:24Z

release-policies.md


-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.


"Release Candidate" should be changed to "Go-Live"

leecow · 2022-10-25T20:44:27Z

release-policies.md

+* **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.


"End of support" should be "End of life"

release-policies.md

Co-authored-by: Jamshed Damkewala <[email protected]>

release-policies.md

release-notes/7.0/README.md

release-notes/7.0/supported-os.md

release-policies.md

releases.md

Switch to 'sts' for short term releases

9f16d5e

richlander requested review from dcwhittaker, leecow and rbhanda as code owners June 4, 2022 20:14

dcwhittaker approved these changes Jun 6, 2022

View reviewed changes

YuliiaKovalova mentioned this pull request Jul 1, 2022

Update potential values for Channel arg dotnet/install-scripts#289

Closed

richlander mentioned this pull request Jul 15, 2022

Update Current -> STS #7602

Closed

richlander added 5 commits July 15, 2022 09:34

Update release policies

0f2ceac

Update supported OS links

7cfb574

Update supported OS links

3d12194

Merge branch 'main' into sts

ed18713

Update release-policies.md

7825f5c

Falco20019 reviewed Aug 24, 2022

View reviewed changes

release-policies.md Outdated Show resolved Hide resolved

Falco20019 reviewed Aug 24, 2022

View reviewed changes

release-policies.md Outdated Show resolved Hide resolved

mairaw and others added 2 commits October 13, 2022 16:23

Apply suggestions from code review

c70bd9f

Co-authored-by: Genevieve Warren <[email protected]>

sts->standard

634afa9

mairaw changed the title ~~Switch to 'sts' for short term releases~~ Switch to standard support releases Oct 13, 2022

Merge branch 'main' into sts

174d64f

gewarren approved these changes Oct 14, 2022

View reviewed changes

mairaw and others added 4 commits October 19, 2022 18:02

more updates

e2c2d2d

feedback

682db40

remove extra space

06230d7

Apply suggestions from code review

2c2c156

Co-authored-by: Genevieve Warren <[email protected]>

jamshedd requested changes Oct 20, 2022

View reviewed changes

leecow requested changes Oct 25, 2022

View reviewed changes

Update release-policies.md

3c36145

Co-authored-by: Jamshed Damkewala <[email protected]>