core
core copied to clipboard
dotnet
Switch to 'sts' for short term releases
The "Current" term is switching to "Short Term Support (STS)". It nicely and intuitively contrasts with "Long Term Support (LTS)". Nothing else is changing (beyond the name).
Relates to:
- https://github.com/dotnet/designs/blob/main/accepted/2022/dotnet-release-labels.md
- https://github.com/dotnet/core/pull/7499
I'll merge this in a bit. I'm going to publish a breaking change announcement, first.
I also need to update docs. I'll create a PR on that next week. We can merge that one coordinated with the website.
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.
@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?
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 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 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 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.
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.