Update release notes format (#6100)

* Update release notes

* Update release notes

* Update .NET 6 releae notes

* Update table

* Update links

* Update release table

* Update 2.1

* Update table

* Update links

* Add linux packages doc

* Add link to packages doc

* Update Arch instructions

* Add statement about globalization invariant mode

* Apply suggestions from code review

Co-authored-by: Michael Simons <msimons@microsoft.com>
Co-authored-by: Matt Thalman <mthalman@microsoft.com>

* Update per feedback

* Update link

* Add buster

* Update heading

* Cleanup wording

* Update per feedback

* Update per feedback

* Apply suggestions from code review

Co-authored-by: Maira Wenzel <mairaw@microsoft.com>

* Update perf feedback

* Update release-policies.md

Co-authored-by: Maira Wenzel <mairaw@microsoft.com>

Co-authored-by: Michael Simons <msimons@microsoft.com>
Co-authored-by: Matt Thalman <mthalman@microsoft.com>
Co-authored-by: Maira Wenzel <mairaw@microsoft.com>

1 files changed, 10 insertions, 12 deletions

diff --git a/release-policies.md b/release-policies.md
index bd437229..7677f213 100644
--- a/release-policies.md
+++ b/release-policies.md
@@ -8,16 +8,17 @@ New major .NET versions are released annually in November. .NET 5.0 was the firs
 
 ## Release types
 
-Each .NET release is defined (prior to initial release) as either **Long Term Support (LTS)** or **Current**. The difference is support time frame, as defined below:
+Each .NET release is defined (prior to initial release) as either **Preview**, **Current**, or **Long Term Support (LTS)**. The difference is support time frame, as defined below:
 
-* **LTS** releases are supported for three years. They are intended for users that want the stability and lower cost of maintaining an application on a single (major.minor) .NET version for an extended period.
+* **Preview** releases are not supported but are offered for public testing. A Preview or Release Candidate release may be considered "go live" and have its own specific ad-hoc support terms that aren't covered by this general policy.
 * **Current** releases are supported for (typically) fifteen months. They are intended for users that want to take advantage of the newest features and improvements and to stay on the leading edge of .NET innovation. Current release users need to upgrade to later .NET releases more often to stay in support.
+* **LTS** releases are supported for three years. They are intended for users that want the stability and lower cost of maintaining an application on a single (major.minor) .NET version for an extended period.
 
 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.
 
-## Servicing periods
+## Servicing
 
-.NET Core releases are supported -- during the servicing period -- according to the following policies. Servicing policies are the same for LTS and Current releases.
+.NET releases are supported -- during the servicing period -- according to the following policies. Servicing policies are the same for LTS and Current releases.
 
 A single "bug bar" is used to decide if a change is warranted and safe for servicing updates. A given fix is often applied to multiple [servicing branches](https://github.com/dotnet/core/blob/main/daily-builds.md#servicing-releases), independent of release type. Breaking changes are not accepted during servicing, except (in the very rare case) to resolve a security vulnerability.
 
@@ -38,20 +39,17 @@ Functional improvements are typically very targeted, and may address the followi
 
 During the maintenance support period, .NET releases are updated to mitigate security vulnerabilities, only.
 
+* Current releases are supported for fifteen months, the last three months of which is maintenance.
+* LTS releases are supported for three years, the last year of which is maintenance.
+
+After the maintenance period ends, the release is out of support.
+
 ### End of support
 
 "End of support", "out of support", or "end of life" refers to the date after which fixes, updates, or technical assistance are no longer provided. As the end of support nears for a given .NET version, we recommend that you move to a newer .NET version, and reduce/remove your use of the given .NET version. After support ends, we recommend that you uninstall a given .NET version if you are no longer using it, or install the latest patch, and accelerate your plans to remove your use of that .NET version.
 
 Your use of out-of-support .NET versions may put your applications, application data, and computing environment at risk. You are strongly recommended to not use out-of-support software.
 
-## Support Policies
-
-The following policies are used to determine support length and kind.
-
-* LTS releases are supported for three years. They receive full support for the first two years and are in maintenance for the third year. After that time, the release will be out-of-support.
-* Current releases are typically supported for fifteen months. They receive full support for the first twelve months and are in maintenance for the last three months. After that time, the release will be out-of-support.
-* A Current release will be supported for a shorter period if a new release (LTS or Current) is released within twelve months of that Current release. In that case, the Current release will immediately transition to three months of maintenance support. After that time, the release will be out-of-support.
-
 ## Vendor support
 
 [Microsoft offers support](microsoft-support.md) for in-support releases. Updates are provided at [dotnet.microsoft.com](https://dotnet.microsoft.com/download/dotnet) and [Microsoft Update](https://devblogs.microsoft.com/dotnet/net-core-updates-coming-to-microsoft-update/).