Skip to content

Commit b4cf24a

Browse files
authored
More Eamon suggestions
@eamonoreilly
1 parent 184e9d7 commit b4cf24a

File tree

1 file changed

+3
-11
lines changed

1 file changed

+3
-11
lines changed

articles/azure-functions/language-support-policy.md

Lines changed: 3 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -11,21 +11,19 @@ This article explains Azure functions language runtime support policy.
1111

1212
## Retirement process
1313

14-
Azure Functions runtime is built around various components, including operating systems, the Azure Functions host, and language-specific workers. To maintain full support coverages for function apps, Azure Functions uses a phased reduction in support as programming language versions reach their end-of-life dates. For most language versions, the retirement date coincides with the community end-of-life date.
14+
Azure Functions runtime is built around various components, including operating systems, the Azure Functions host, and language-specific workers. To maintain full support coverages for function apps, Azure Functions support aligns with end-of-life support for a given language. To acheive this, Functions implements a phased reduction in support as programming language versions reach their end-of-life dates. For most language versions, the retirement date coincides with the community end-of-life date.
1515

1616
### Notification phase
1717

1818
We'll send notification emails to function app users about upcoming language version retirements. The notifications will be at least one year before the date of retirement. Upon the notification, you should prepare to upgrade the language version that your functions apps use to a supported version.
1919

2020
### Retirement phase
2121

22-
Starting on the end-of-life date for a language version, you can no longer create new function apps targeting that language version.
23-
24-
After the language end-of-life date, function apps that use retired language versions won't be eligible for new features, security patches, and performance optimizations. However, these function apps will continue to run on the platform.
22+
After the language end-of-life date, function apps that use retired language versions can still be created and continue to run on the platform, however they won't be eligible for new features, security patches, and performance optimizations.
2523

2624
> [!IMPORTANT]
2725
>You're highly encouraged to upgrade the language version of your affected function apps to a supported version.
28-
>If you're running functions apps using an unsupported language version, you'll be required to upgrade before receiving support for the function apps.
26+
>If you're running functions apps using an unsupported language version, you'll be required to upgrade before receiving support for your function app.
2927
3028

3129
## Retirement policy exceptions
@@ -34,15 +32,9 @@ There are few exceptions to the retirement policy outlined above. Here is a list
3432

3533
|Language Versions |EOL Date |Retirement Date|
3634
|-----------------------------------------|-----------------|----------------|
37-
|.NET 5|8 May 2022|TBA|
38-
|Node 6|30 April 2019|28 February 2022|
39-
|Node 8|31 December 2019|28 February 2022|
40-
|Node 10|30 April 2021|30 September 2022|
41-
|Node 12|30 Apr 2022|TBA|
4235
|PowerShell Core 6| 4 September 2020|30 September 2022|
4336
|Python 3.6 |23 December 2021|30 September 2022|
4437

45-
4638
## Language version support timeline
4739

4840
To learn more about specific language version support policy timeline, visit the following external resources:

0 commit comments

Comments
 (0)