Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Publish to live #11092

Merged
merged 3 commits into from
May 9, 2024
Merged

Publish to live #11092

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
29834e9
Fix <maml:paragraph> elements in cmdlet doc examples to <maml:para>
MatejKafka May 9, 2024
66a5452
Merge pull request #11089 from MatejKafka/main
sdwheeler May 9, 2024
c638925
Refresh support statements (#11091)
sdwheeler May 9, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
24 changes: 12 additions & 12 deletions ...ce/docs-conceptual/developer/help/how-to-add-examples-to-a-cmdlet-help-topic.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -63,9 +63,9 @@ the Windows PowerShell prompt: `C:\PS>`.
<command:examples>
<command:example>
<maml:title>---------- EXAMPLE 1 ----------</maml:title>
<maml:Introduction>
<maml:paragraph>C:\PS></maml:paragraph>
</maml:Introduction>
<maml:introduction>
<maml:para>C:\PS></maml:para>
</maml:introduction>
</command:example>
</command:examples>
```
Expand All @@ -80,9 +80,9 @@ whenever possible.
<command:examples>
<command:example>
<maml:title>---------- EXAMPLE 1 ----------</maml:title>
<maml:Introduction>
<maml:paragraph>C:\PS></maml:paragraph>
</maml:Introduction>
<maml:introduction>
<maml:para>C:\PS></maml:para>
</maml:introduction>
<dev:code> command </dev:code>
</command:example>
</command:examples>
Expand All @@ -97,9 +97,9 @@ The following XML shows how to add a description for the example. PowerShell use
<command:examples>
<command:example>
<maml:title>---------- EXAMPLE 1 ----------</maml:title>
<maml:Introduction>
<maml:paragraph>C:\PS></maml:paragraph>
</maml:Introduction>
<maml:introduction>
<maml:para>C:\PS></maml:para>
</maml:introduction>
<dev:code> command </dev:code>
<dev:remarks>
<maml:para> command description </maml:para>
Expand All @@ -119,9 +119,9 @@ command.
<command:examples>
<command:example>
<maml:title>---------- EXAMPLE 1 ----------</maml:title>
<maml:Introduction>
<maml:paragraph>C:\PS></maml:paragraph>
</maml:Introduction>
<maml:introduction>
<maml:para>C:\PS></maml:para>
</maml:introduction>
<dev:code> command </dev:code>
<dev:remarks>
<maml:para> command description </maml:para>
Expand Down
134 changes: 67 additions & 67 deletions reference/docs-conceptual/install/PowerShell-Support-Lifecycle.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
---
description: Details the policies governing support for PowerShell
ms.date: 05/08/2024
description: Details the policies governing support for PowerShell.
ms.date: 05/09/2024
ms.topic: lifecycle
title: PowerShell Support Lifecycle
---
Expand All @@ -16,7 +16,7 @@ linked to [.NET and .NET Core Support Policy][06]. In this servicing approach, c
Long Term Support (LTS) releases or current releases.

An **LTS** release of PowerShell is built on an LTS release of .NET. Updates to an LTS release only
contain critical security updates and servicing fixes that are designed to minimize impact to
contain critical security updates and servicing fixes that are designed to minimize impact on
existing workloads. LTS releases of PowerShell are supported until the end-of-support for .NET.

A **current** release is a release that occurs between LTS releases. Current releases can contain
Expand All @@ -30,18 +30,23 @@ the next release (current or LTS).

## Supported platforms

PowerShell runs on multiple operating systems (OS) and processor architectures. To be supported by
Microsoft, the OS must meet the following criteria:
PowerShell runs on multiple operating systems (OS) and processor architectures. For support, the
platform must meet the following criteria:

- The version and processor architecture of the OS is supported by .NET Core.
- The version of the OS is supported for at least one year.
- The version of the OS isn't an interim release or equivalent.
- The version of the OS is currently supported by the OS publisher.
- The PowerShell team has tested the version of the distribution.
- The target platform (OS version and processor architecture) is supported by .NET.
- The OS version is supported by the distributor for at least one year.
- The OS version isn't an interim release or equivalent.
- The OS version is currently supported by the distributor.
- Microsoft has tested and approved PowerShell on the target platform.

When a platform version reaches end-of-life as defined by the platform owner, PowerShell also ends
support on that platform version. Previously released packages remain available for customers
needing access but formal support and updates of any kind are no longer be provided.
Support for PowerShell ends when either of the following conditions are met:

- The target platform reaches end-of-life as defined by the platform owner
- The specific version of PowerShell reaches end-of-life

After a version of PowerShell reaches end-of-life, no further updates, including security updates,
are provided. Microsoft encourages customers to upgrade to a supported version of PowerShell to
continue receiving updates and support.

### Windows

Expand Down Expand Up @@ -80,46 +85,39 @@ feedback on experimental features and we provide best-effort support for them.

## Notes on licensing

PowerShell is released under the [MIT license][10]. Under this license, and without a paid support
PowerShell is released under the [MIT license][15]. Under this license, and without a paid support
agreement, users are limited to [community support][04]. With community support, Microsoft makes no
guarantees of responsiveness or fixes.

## Getting support

Support for PowerShell is delivered via traditional Microsoft support agreements, including
[paid support][12], [Microsoft Enterprise Agreements][14], and [Microsoft Software Assurance][15].
You can also pay for [assisted support][11] for PowerShell by filing a support request for your
problem.
Support for PowerShell is provided on a best-effort basis. Support for Windows PowerShell 5.1 is
provided through Windows support channels. You can use the standard paid support channels to get
support for PowerShell.

There are multiple [community support][04] options. You can file an issue, bug, or feature request on
GitHub. Also, you can get help from other members of the community in the Microsoft
[PowerShell Tech Community][13] or any of the community forums listed on the [PowerShell][04] hub
page. If you have a problem that requires immediate attention, you should use the traditional, paid
support options.
- [Support for business][18]
- [Contact support][17]

> [!IMPORTANT]
> You must have the latest patch update installed to qualify for support. For example, if you're
> running PowerShell 7.3 and 7.3.1 has been released, you must update to 7.3.1 to qualify for
> support.
There are many free support options available from the PowerShell community. The most active
community support channels are available through **Discord** or **Slack**. The discussion channels
are mirrored on both platforms, so you can choose the platform that you prefer. These channels can
help you troubleshoot issues, answer questions, and provide guidance on how to use PowerShell.

If you think that you found a bug, you can file an issue on [GitHub][16]. The PowerShell team can't
provide support through GitHub, but they welcome bug reports. The [community support][04] page
provides links to the most popular community support channels.

## PowerShell End-of-support dates
## PowerShell end-of-support dates

Based on these lifecycle policies, the following table lists the dates when support for the current
versions of PowerShell end:
The PowerShell support lifecycle is tied to the [support lifecycle of .NET][06]. The following table
lists the end-of-support dates for the current versions of PowerShell:

| Version | Release Date | End-of-support |
| ------------------ | ----------------- | ----------------- |
| 7.4 (LTS-current) | November 16, 2023 | November 10, 2026 |
| 7.2 (LTS-previous) | November 8, 2021 | November 8, 2024 |

Support for PowerShell on a specific platform is based on the support policy of the version of .NET
used.

- PowerShell 7.4 (LTS-current) is based on the [.NET 8.0 Supported OS Lifecycle Policy][09]
- PowerShell 7.3 (Stable) is based on the [.NET 7.0 Supported OS Lifecycle Policy][08]
- PowerShell 7.2 (LTS-previous) is based on the [.NET 6.0 Supported OS Lifecycle Policy][07]

End of support dates for already retired versions were:
The following table lists the end-of-support dates for retired versions of PowerShell:

| Version | Release Date | End-of-support |
| --------- | ------------------ | ------------------ |
Expand All @@ -132,26 +130,25 @@ End of support dates for already retired versions were:

## Release history

The following table contains a timeline of the major releases of PowerShell. This table is provided
for historical reference. It isn't intended for use to determine the support lifecycle.

| Version | Release Date | Note |
| ----------------------------- | :----------: | ------------------------------------------------------------------------------- |
| PowerShell 7.5 (preview) | TBA | Built on .NET 9.0.0-preview.1 |
| PowerShell 7.4 (LTS-current) | Nov-2023 | Built on .NET 8.0.0 |
| PowerShell 7.3 | Nov-2022 | Built on .NET 7.0 |
| PowerShell 7.2 (LTS-previous) | Nov-2021 | Built on .NET 6.0 (LTS-previous) |
| PowerShell 7.1 | Nov-2020 | Built on .NET 5.0 |
| PowerShell 7.0 (LTS) | Mar-2020 | Built on .NET Core 3.1 (LTS) |
| PowerShell 6.2 | Mar-2019 | Built on .NET Core 2.1 |
| PowerShell 6.1 | Sep-2018 | Built on .NET Core 2.1 |
| PowerShell 6.0 | Jan-2018 | First release, built on .NET Core 2.0. Installable on Windows, Linux, and macOS |
| Windows PowerShell 5.1 | Aug-2016 | Released in Windows 10 Anniversary Update and Windows Server 2016, WMF 5.1 |
| Windows PowerShell 5.0 | Feb-2016 | Released in Windows Management Framework (WMF) 5.0 |
| Windows PowerShell 4.0 | Oct-2013 | Integrated in Windows 8.1 and with Windows Server 2012 R2, WMF 4.0 |
| Windows PowerShell 3.0 | Oct-2012 | Integrated in Windows 8 and with Windows Server 2012 WMF 3.0 |
| Windows PowerShell 2.0 | Jul-2009 | Integrated in Windows 7 and Windows Server 2008 R2, WMF 2.0 |
| Windows PowerShell 1.0 | Nov-2006 | Optional component of Windows Server 2008 |
The following table contains a historical timeline of the major releases of PowerShell.

| Version | Release Date | Note |
| ----------------------------- | :----------: | -------------------------------------------------------------------------- |
| PowerShell 7.5 (preview) | Future | Built on [.NET 9.0.0][14] |
| PowerShell 7.4 (LTS-current) | Nov-2023 | Built on [.NET 8.0.0][13] |
| PowerShell 7.3 | Nov-2022 | Built on [.NET 7.0][12] |
| PowerShell 7.2 (LTS-previous) | Nov-2021 | Built on [.NET 6.0][11] |
| PowerShell 7.1 | Nov-2020 | Built on [.NET 5.0][10] |
| PowerShell 7.0 (LTS) | Mar-2020 | Built on [.NET Core 3.1][09] |
| PowerShell 6.2 | Mar-2019 | Built on [.NET Core 2.1][08] |
| PowerShell 6.1 | Sep-2018 | Built on [.NET Core 2.1][08] |
| PowerShell 6.0 | Jan-2018 | Built on [.NET Core 2.0][07]. Installable on Windows, Linux, and macOS |
| Windows PowerShell 5.1 | Aug-2016 | Released in Windows 10 Anniversary Update and Windows Server 2016, WMF 5.1 |
| Windows PowerShell 5.0 | Feb-2016 | Released in Windows Management Framework (WMF) 5.0 |
| Windows PowerShell 4.0 | Oct-2013 | Released in Windows 8.1 and with Windows Server 2012 R2, WMF 4.0 |
| Windows PowerShell 3.0 | Oct-2012 | Released in Windows 8 and with Windows Server 2012 WMF 3.0 |
| Windows PowerShell 2.0 | Jul-2009 | Released in Windows 7 and Windows Server 2008 R2, WMF 2.0 |
| Windows PowerShell 1.0 | Nov-2006 | Released as optional component of Windows Server 2008 |

Run the following command to see the full version number of .NET used by the version of PowerShell
you're running:
Expand All @@ -167,12 +164,15 @@ you're running:
[04]: /powershell/scripting/community/community-support
[05]: /powershell/scripting/learn/experimental-features
[06]: https://dotnet.microsoft.com/platform/support/policy/dotnet-core
[07]: https://github.com/dotnet/core/blob/main/release-notes/6.0/supported-os.md
[08]: https://github.com/dotnet/core/blob/main/release-notes/7.0/supported-os.md
[09]: https://github.com/dotnet/core/blob/main/release-notes/8.0/supported-os.md
[10]: https://github.com/PowerShell/PowerShell/blob/master/LICENSE.txt
[11]: https://support.microsoft.com/supportforbusiness/productselection
[12]: https://support.serviceshub.microsoft.com/supportforbusiness
[13]: https://techcommunity.microsoft.com/t5/PowerShell/ct-p/WindowsPowerShell
[14]: https://www.microsoft.com/licensing/licensing-programs/enterprise
[15]: https://www.microsoft.com/licensing/licensing-programs/software-assurance-default
[07]: https://github.com/dotnet/core/blob/main/release-notes/2.0/2.0-supported-os.md
[08]: https://github.com/dotnet/core/blob/main/release-notes/2.1/2.1-supported-os.md
[09]: https://github.com/dotnet/core/blob/main/release-notes/3.1/3.1-supported-os.md
[10]: https://github.com/dotnet/core/blob/main/release-notes/5.0/5.0-supported-os.md
[11]: https://github.com/dotnet/core/blob/main/release-notes/6.0/supported-os.md
[12]: https://github.com/dotnet/core/blob/main/release-notes/7.0/supported-os.md
[13]: https://github.com/dotnet/core/blob/main/release-notes/8.0/supported-os.md
[14]: https://github.com/dotnet/core/blob/main/release-notes/9.0/supported-os.md
[15]: https://github.com/PowerShell/PowerShell/blob/master/LICENSE.txt
[16]: https://github.com/PowerShell/PowerShell/issues/new/choose
[17]: https://support.microsoft.com/contactus
[18]: https://support.serviceshub.microsoft.com/