Skip to content

Commit a3fca1f

Browse files
committed
fix the deprecation period
1 parent ff1b71f commit a3fca1f

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/azure-functions/extension-bundles.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,7 @@ You define an extension bundle reference in the *host.json* project file by addi
2727

2828
## Supported extension bundles
2929

30-
This table lists all `Microsoft.Azure.Functions.ExtensionBundle` bundle versions and the current [support status](#support-policy).
30+
This table lists all `Microsoft.Azure.Functions.ExtensionBundle` bundle versions and the current [support state](#support-policy).
3131

3232
| Bundle version | Version in host.json | Support state | End-of-support date |
3333
| --- | --- | --- | --- |
@@ -79,7 +79,7 @@ The support cycle of a GA extension bundle follows these phases:
7979
| ----- | ----- |
8080
| Active | This phase is for the latest GA extension bundle version, which is the recommended version for your function apps. Bundle versions remain active for at least 12 months after being declared GA. |
8181
| Notification| Microsoft provides advanced notice before retiring an extension bundle or binding extension version. When you receive such a notification, you should begin planning to upgrade your function apps to a latest supported extension bundle version. This upgrade ensures that your apps continue to access new features, performance improvements, and support. |
82-
| Deprecation phase | Occurs 12 months after the next major extension bundle version is declared to be GA. This overlap period gives you time to plan, test, and upgrade your apps before the previous version is retired. |
82+
| Deprecation phase | Starts when the next major extension bundle version is declared to be GA and continues for 12 months. This overlap period gives you time to plan, test, and upgrade your apps before the previous version is retired. |
8383
| Retirement phase | After the retirement of an extension bundle or binding extension version, function apps that use retired versions can still be created and deployed and continue to run on the platform. However, your function apps aren’t eligible for new features, security patches, and performance optimizations until you upgrade them to use a supported extension bundle version. You must upgrade your functions apps to a supported bundle version before you can receive support.|
8484

8585
You can view the extension bundle versions and their included extensions in the [Azure Functions Extension Bundles GitHub repo](https://github.com/Azure/azure-functions-extension-bundles/releases). Individual .NET packages are found on [https://nuget.org](https://nuget.org).

0 commit comments

Comments
 (0)