From 213ef405c3dc50aaf984958f34798f6383c7137e Mon Sep 17 00:00:00 2001 From: Leandro Damascena Date: Tue, 30 Jan 2024 10:04:33 +0000 Subject: [PATCH 1/7] Adding versioning policy --- docs/versioning.md | 68 ++++++++++++++++++++++++++++++++++++++++++++++ mkdocs.yml | 1 + 2 files changed, 69 insertions(+) create mode 100644 docs/versioning.md diff --git a/docs/versioning.md b/docs/versioning.md new file mode 100644 index 00000000000..3e762180783 --- /dev/null +++ b/docs/versioning.md @@ -0,0 +1,68 @@ +--- +title: Versioning and maintenance policy +description: Versioning and maintenance policy for Powertools for AWS Lambda (Python) +--- + + + +### Overview + +This document outlines the maintenance policy for AWS Software Development Kits (SDKs) and Tools, including Mobile and IoT SDKs, and their underlying dependencies. AWS regularly provides the AWS SDKs and Tools with updates that may contain support for new or updated AWS APIs, new features, enhancements, bug fixes, security patches, or documentation updates. Updates may also address changes with dependencies, language runtimes, and operating systems. AWS SDK releases are published to package managers (e.g. Maven, NuGet, PyPI), and are available as source code on GitHub. + +We recommend users to stay up-to-date with SDK releases to keep up with the latest features, security updates, and underlying dependencies. Continued use of an unsupported SDK version is not recommended and is done at the user’s discretion. + +### Versioning + +The AWS SDK release versions are in the form of X.Y.Z where X represents the major version. Increasing the major version of an SDK indicates that this SDK underwent significant and substantial changes to support new idioms and patterns in the language. Major versions are introduced when public interfaces (e.g. classes, methods, types, etc.), behaviors, or semantics have changed. Applications need to be updated in order for them to work with the newest SDK version. It is important to update major versions carefully and in accordance with the upgrade guidelines provided by AWS. + +### SDK major version lifecycle + +The lifecycle for major SDKs and Tools versions consists of 5 phases, which are outlined below. + +* _Developer Preview (Phase 0) -_ During this phase, SDKs are not supported, should not be used in production environments, and are meant for early access and feedback purposes only. It is possible for future releases to introduce breaking changes. Once AWS identifies a release to be a stable product, it may mark it as a Release Candidate. Release Candidates are ready for GA release unless significant bugs emerge, and will receive full AWS support. + +* _General Availability (GA) (Phase 1) -_ During this phase, SDKs are fully supported. AWS will provide regular SDK releases that include support for new services, API updates for existing services, as well as bug and security fixes. For Tools, AWS will provide regular releases that include new feature updates and bug fixes. AWS will support the GA version of an SDK for _at least 24 months_. + +* _Maintenance Announcement (Phase 2) -_ AWS will make a public announcement at least 6 months before an SDK enters maintenance mode. During this period, the SDK will continue to be fully supported. Typically, maintenance mode is announced at the same time as the next major version is transitioned to GA. + +* _Maintenance (Phase 3) -_ During the maintenance mode, AWS limits SDK releases to address critical bug fixes and security issues only. An SDK will not receive API updates for new or existing services, or be updated to support new regions. Maintenance mode has a _default duration of 12 months_, unless otherwise specified. + +* _End-of-Support (Phase 4) -_ When an SDK reaches end-of support, it will no longer receive updates or releases. Previously published releases will continue to be available via public package managers and the code will remain on GitHub. The GitHub repository may be archived. Use of an SDK which has reached end-of-support is done at the user’s discretion. We recommend users upgrade to the new major version. + +_The following is a visual illustration of the SDK major version lifecycle. Please note that the timelines shown below are illustrative and not binding._ + +![ +Maintenance policy timelines +](https://docs.aws.amazon.com/images/sdkref/latest/guide/images/maint-policy.png) + +### Dependency lifecycle + +Most AWS SDKs have underlying dependencies, such as language runtimes, operating systems, or third party libraries and frameworks. These dependencies are typically tied to the language community or the vendor who owns that particular component. Each community or vendor publishes their own end-of-support schedule for their product. + +The following terms are used to classify underlying third party dependencies: + +* _Operating System (OS):_ Examples include Amazon Linux AMI, Amazon Linux 2, Windows 2008, Windows 2012, Windows 2016, etc. + +* _Language Runtime:_ Examples include Java 7, Java 8, Java 11, .NET Core, .NET Standard, .NET PCL, etc. + +* _Third party Library / Framework:_ Examples include OpenSSL, .NET Framework 4.5, Java EE, etc. + +Our policy is to continue supporting SDK dependencies for at least 6 months after the community or vendor ends support for the dependency. This policy, however, could vary depending on the specific dependency. + +### Note + +[BANNER] AWS reserves the right to stop support for an underlying dependency without increasing the major SDK version + +### Communication methods + +Maintenance announcements are communicated in several ways: + +* An email announcement is sent to affected accounts, announcing our plans to end support for the specific SDK version. The email will outline the path to end-of-support, specify the campaign timelines, and provide upgrade guidance. + +* AWS SDK documentation, such as API reference documentation, user guides, SDK product marketing pages, and GitHub readme(s) are updated to indicate the campaign timeline and provide guidance on upgrading affected applications. + +* An AWS blog post is published that outlines the path to end-of-support, as well as reiterates the campaign timelines. + +* Deprecation warnings are added to the SDKs, outlining the path to end-of-support and linking to the SDK documentation. + +To see the list of available major versions of AWS SDKs and Tools and where they are in their maintenance lifecycle, see [AWS SDKs and Tools version support matrix](https://docs.aws.amazon.com/sdkref/latest/guide/version-support-matrix.html). diff --git a/mkdocs.yml b/mkdocs.yml index 0a844fd392f..a862430a054 100644 --- a/mkdocs.yml +++ b/mkdocs.yml @@ -38,6 +38,7 @@ nav: - Processes: - Security: security.md - Automation: automation.md + - Versioning policy: versioning.md - Roadmap: roadmap.md - Maintainers: maintainers.md - Contributing: From 50d1ce8e43a65bdf95d6a3b769f4a7786e66d01b Mon Sep 17 00:00:00 2001 From: heitorlessa Date: Tue, 30 Jan 2024 11:52:26 +0100 Subject: [PATCH 2/7] docs: update wording to reflect Powertools for AWS Lambda --- docs/versioning.md | 57 +++++++++++++++++++++------------------------- 1 file changed, 26 insertions(+), 31 deletions(-) diff --git a/docs/versioning.md b/docs/versioning.md index 3e762180783..cfbe98aac68 100644 --- a/docs/versioning.md +++ b/docs/versioning.md @@ -7,62 +7,57 @@ description: Versioning and maintenance policy for Powertools for AWS Lambda (Py ### Overview -This document outlines the maintenance policy for AWS Software Development Kits (SDKs) and Tools, including Mobile and IoT SDKs, and their underlying dependencies. AWS regularly provides the AWS SDKs and Tools with updates that may contain support for new or updated AWS APIs, new features, enhancements, bug fixes, security patches, or documentation updates. Updates may also address changes with dependencies, language runtimes, and operating systems. AWS SDK releases are published to package managers (e.g. Maven, NuGet, PyPI), and are available as source code on GitHub. +This document outlines the maintenance policy for Powertools for AWS Lambda and their underlying dependencies. AWS regularly provides Powertools for AWS Lambda with updates that may contain new features, enhancements, bug fixes, security patches, or documentation updates. Updates may also address changes with dependencies, language runtimes, and operating systems. Powertools for AWS Lambda is published to package managers (e.g. PyPi, NPM, Maven, NuGet), and are available as source code on GitHub. -We recommend users to stay up-to-date with SDK releases to keep up with the latest features, security updates, and underlying dependencies. Continued use of an unsupported SDK version is not recommended and is done at the user’s discretion. +We recommend users to stay up-to-date with Powertools for AWS Lambda releases to keep up with the latest features, security updates, and underlying dependencies. Continued use of an unsupported Powertools for AWS Lambda version is not recommended and is done at the user’s discretion. + +!!! info "For brevity, we will interchangeably refer to Powertools for AWS Lambda as "SDK" _(Software Development Toolkit)_." ### Versioning -The AWS SDK release versions are in the form of X.Y.Z where X represents the major version. Increasing the major version of an SDK indicates that this SDK underwent significant and substantial changes to support new idioms and patterns in the language. Major versions are introduced when public interfaces (e.g. classes, methods, types, etc.), behaviors, or semantics have changed. Applications need to be updated in order for them to work with the newest SDK version. It is important to update major versions carefully and in accordance with the upgrade guidelines provided by AWS. +Powertools for AWS Lambda release versions are in the form of X.Y.Z where X represents the major version. Increasing the major version of an SDK indicates that this SDK underwent significant and substantial changes to support new idioms and patterns in the language. Major versions are introduced when public interfaces _(e.g. classes, methods, types, etc.)_, behaviors, or semantics have changed. Applications need to be updated in order for them to work with the newest SDK version. It is important to update major versions carefully and in accordance with the upgrade guidelines provided by AWS. ### SDK major version lifecycle -The lifecycle for major SDKs and Tools versions consists of 5 phases, which are outlined below. - -* _Developer Preview (Phase 0) -_ During this phase, SDKs are not supported, should not be used in production environments, and are meant for early access and feedback purposes only. It is possible for future releases to introduce breaking changes. Once AWS identifies a release to be a stable product, it may mark it as a Release Candidate. Release Candidates are ready for GA release unless significant bugs emerge, and will receive full AWS support. - -* _General Availability (GA) (Phase 1) -_ During this phase, SDKs are fully supported. AWS will provide regular SDK releases that include support for new services, API updates for existing services, as well as bug and security fixes. For Tools, AWS will provide regular releases that include new feature updates and bug fixes. AWS will support the GA version of an SDK for _at least 24 months_. +The lifecycle for major Powertools for AWS Lambda versions consists of 5 phases, which are outlined below. -* _Maintenance Announcement (Phase 2) -_ AWS will make a public announcement at least 6 months before an SDK enters maintenance mode. During this period, the SDK will continue to be fully supported. Typically, maintenance mode is announced at the same time as the next major version is transitioned to GA. +* **Developer Preview** (Phase 0) - During this phase, SDKs are not supported, should not be used in production environments, and are meant for early access and feedback purposes only. It is possible for future releases to introduce breaking changes. Once AWS identifies a release to be a stable product, it may mark it as a Release Candidate. Release Candidates are ready for GA release unless significant bugs emerge, and will receive full AWS support. +* **General Availability (GA)** (Phase 1) - During this phase, SDKs are fully supported. AWS will provide regular SDK releases that include support for new features, enhancements, as well as bug and security fixes. AWS will support the GA version of an SDK for _at least 24 months_. +* **Maintenance Announcement** (Phase 2) - AWS will make a public announcement at least 6 months before an SDK enters maintenance mode. During this period, the SDK will continue to be fully supported. Typically, maintenance mode is announced at the same time as the next major version is transitioned to GA. +* **Maintenance** (Phase 3) - During the maintenance mode, AWS limits SDK releases to address critical bug fixes and security issues only. An SDK will not receive API updates for new or existing services, or be updated to support new regions. Maintenance mode has a _default duration of 12 months_, unless otherwise specified. +* **End-of-Support** (Phase 4) - When an SDK reaches end-of support, it will no longer receive updates or releases. Previously published releases will continue to be available via public package managers and the code will remain on GitHub. The GitHub repository may be archived. Use of an SDK which has reached end-of-support is done at the user’s discretion. We recommend users upgrade to the new major version. -* _Maintenance (Phase 3) -_ During the maintenance mode, AWS limits SDK releases to address critical bug fixes and security issues only. An SDK will not receive API updates for new or existing services, or be updated to support new regions. Maintenance mode has a _default duration of 12 months_, unless otherwise specified. +!!! note "Please note that the timelines shown below are illustrative and not binding" -* _End-of-Support (Phase 4) -_ When an SDK reaches end-of support, it will no longer receive updates or releases. Previously published releases will continue to be available via public package managers and the code will remain on GitHub. The GitHub repository may be archived. Use of an SDK which has reached end-of-support is done at the user’s discretion. We recommend users upgrade to the new major version. - -_The following is a visual illustration of the SDK major version lifecycle. Please note that the timelines shown below are illustrative and not binding._ - -![ -Maintenance policy timelines -](https://docs.aws.amazon.com/images/sdkref/latest/guide/images/maint-policy.png) +![Maintenance policy timelines](https://docs.aws.amazon.com/images/sdkref/latest/guide/images/maint-policy.png) ### Dependency lifecycle -Most AWS SDKs have underlying dependencies, such as language runtimes, operating systems, or third party libraries and frameworks. These dependencies are typically tied to the language community or the vendor who owns that particular component. Each community or vendor publishes their own end-of-support schedule for their product. +Most AWS SDKs have underlying dependencies, such as language runtimes, AWS Lambda runtime, or third party libraries and frameworks. These dependencies are typically tied to the language community or the vendor who owns that particular component. Each community or vendor publishes their own end-of-support schedule for their product. The following terms are used to classify underlying third party dependencies: -* _Operating System (OS):_ Examples include Amazon Linux AMI, Amazon Linux 2, Windows 2008, Windows 2012, Windows 2016, etc. - -* _Language Runtime:_ Examples include Java 7, Java 8, Java 11, .NET Core, .NET Standard, .NET PCL, etc. - -* _Third party Library / Framework:_ Examples include OpenSSL, .NET Framework 4.5, Java EE, etc. +* [**AWS Lambda Runtime**](https://docs.aws.amazon.com/lambda/latest/dg/lambda-runtimes.html): Examples include `nodejs20.x`, `python3.12`, etc. +* **Language Runtime**: Examples include Python 3.12, NodeJS 20, Java 17, .NET Core, etc. +* **Third party Library**: Examples include Pydantic, AWS X-Ray SDK, AWS Encryption SDK, MiddyJS, etc. Our policy is to continue supporting SDK dependencies for at least 6 months after the community or vendor ends support for the dependency. This policy, however, could vary depending on the specific dependency. -### Note - -[BANNER] AWS reserves the right to stop support for an underlying dependency without increasing the major SDK version +!!! note "AWS reserves the right to stop support for an underlying dependency without increasing the major SDK version" ### Communication methods Maintenance announcements are communicated in several ways: -* An email announcement is sent to affected accounts, announcing our plans to end support for the specific SDK version. The email will outline the path to end-of-support, specify the campaign timelines, and provide upgrade guidance. - +* A pinned GitHub Request For Comments (RFC) issue indicating the campaign for the next major version. The RFC will outline the path to end-of-support, specify campaign timelines, and upgrade guidance. * AWS SDK documentation, such as API reference documentation, user guides, SDK product marketing pages, and GitHub readme(s) are updated to indicate the campaign timeline and provide guidance on upgrading affected applications. +* Deprecation warnings are added to the SDKs, outlining the path to end-of-support and linking to the SDK documentation. -* An AWS blog post is published that outlines the path to end-of-support, as well as reiterates the campaign timelines. +To see the list of available major versions of Powertools for AWS Lambda and where they are in their maintenance lifecycle, see [version support matrix](#version-support-matrix) -* Deprecation warnings are added to the SDKs, outlining the path to end-of-support and linking to the SDK documentation. +### Version support matrix -To see the list of available major versions of AWS SDKs and Tools and where they are in their maintenance lifecycle, see [AWS SDKs and Tools version support matrix](https://docs.aws.amazon.com/sdkref/latest/guide/version-support-matrix.html). +| SDK | Major version | Current Phase | General Availability Date | Notes | +| -------------------------------- | ------------- | -------------------- | ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Powertools for AWS Lambda Python | 2.x | General Availability | 10/24/2022 | See [Release Notes](https://github.com/aws-powertools/powertools-lambda-python/releases/tag/v2.0.0) | +| Powertools for AWS Lambda Python | 1.x | End of Support | 06/18/2020 | See [RFC](https://github.com/aws-powertools/powertools-lambda-python/issues/1459) and [upgrade guide](https://docs.powertools.aws.dev/lambda/python/latest/upgrade/) | From 9b8d6c5cdc53470d303a3f58a298cbcbe4d5b581 Mon Sep 17 00:00:00 2001 From: heitorlessa Date: Tue, 30 Jan 2024 14:02:43 +0100 Subject: [PATCH 3/7] docs: adjust timelines, refer to tight coupling w/ Lambda runtime policy --- docs/versioning.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/versioning.md b/docs/versioning.md index cfbe98aac68..cf477393661 100644 --- a/docs/versioning.md +++ b/docs/versioning.md @@ -24,7 +24,7 @@ The lifecycle for major Powertools for AWS Lambda versions consists of 5 phases, * **Developer Preview** (Phase 0) - During this phase, SDKs are not supported, should not be used in production environments, and are meant for early access and feedback purposes only. It is possible for future releases to introduce breaking changes. Once AWS identifies a release to be a stable product, it may mark it as a Release Candidate. Release Candidates are ready for GA release unless significant bugs emerge, and will receive full AWS support. * **General Availability (GA)** (Phase 1) - During this phase, SDKs are fully supported. AWS will provide regular SDK releases that include support for new features, enhancements, as well as bug and security fixes. AWS will support the GA version of an SDK for _at least 24 months_. * **Maintenance Announcement** (Phase 2) - AWS will make a public announcement at least 6 months before an SDK enters maintenance mode. During this period, the SDK will continue to be fully supported. Typically, maintenance mode is announced at the same time as the next major version is transitioned to GA. -* **Maintenance** (Phase 3) - During the maintenance mode, AWS limits SDK releases to address critical bug fixes and security issues only. An SDK will not receive API updates for new or existing services, or be updated to support new regions. Maintenance mode has a _default duration of 12 months_, unless otherwise specified. +* **Maintenance** (Phase 3) - During the maintenance mode, AWS limits SDK releases to address critical bug fixes and security issues only. An SDK will not receive API updates for new or existing services, or be updated to support new regions. Maintenance mode has a _default duration of 6 months_, unless otherwise specified. * **End-of-Support** (Phase 4) - When an SDK reaches end-of support, it will no longer receive updates or releases. Previously published releases will continue to be available via public package managers and the code will remain on GitHub. The GitHub repository may be archived. Use of an SDK which has reached end-of-support is done at the user’s discretion. We recommend users upgrade to the new major version. !!! note "Please note that the timelines shown below are illustrative and not binding" @@ -41,7 +41,7 @@ The following terms are used to classify underlying third party dependencies: * **Language Runtime**: Examples include Python 3.12, NodeJS 20, Java 17, .NET Core, etc. * **Third party Library**: Examples include Pydantic, AWS X-Ray SDK, AWS Encryption SDK, MiddyJS, etc. -Our policy is to continue supporting SDK dependencies for at least 6 months after the community or vendor ends support for the dependency. This policy, however, could vary depending on the specific dependency. +Powertools for AWS Lambda follows [AWS Lambda Runtime deprecation policy cycle](https://docs.aws.amazon.com/lambda/latest/dg/lambda-runtimes.html#runtime-support-policy), when it comes to Language Runtime. This means we will stop supporting deprecated Language Runtime without increasing the major SDK version. !!! note "AWS reserves the right to stop support for an underlying dependency without increasing the major SDK version" @@ -51,7 +51,7 @@ Maintenance announcements are communicated in several ways: * A pinned GitHub Request For Comments (RFC) issue indicating the campaign for the next major version. The RFC will outline the path to end-of-support, specify campaign timelines, and upgrade guidance. * AWS SDK documentation, such as API reference documentation, user guides, SDK product marketing pages, and GitHub readme(s) are updated to indicate the campaign timeline and provide guidance on upgrading affected applications. -* Deprecation warnings are added to the SDKs, outlining the path to end-of-support and linking to the SDK documentation. +* Deprecation warnings are added to the SDKs, outlining the path to end-of-support and linking to the upgrade guide. To see the list of available major versions of Powertools for AWS Lambda and where they are in their maintenance lifecycle, see [version support matrix](#version-support-matrix) From 68f153bc2b2e9d363f03d272c160cb30c048a9f0 Mon Sep 17 00:00:00 2001 From: heitorlessa Date: Tue, 30 Jan 2024 14:10:15 +0100 Subject: [PATCH 4/7] docs: fix grammar --- docs/versioning.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/versioning.md b/docs/versioning.md index cf477393661..55bef7c0111 100644 --- a/docs/versioning.md +++ b/docs/versioning.md @@ -41,7 +41,7 @@ The following terms are used to classify underlying third party dependencies: * **Language Runtime**: Examples include Python 3.12, NodeJS 20, Java 17, .NET Core, etc. * **Third party Library**: Examples include Pydantic, AWS X-Ray SDK, AWS Encryption SDK, MiddyJS, etc. -Powertools for AWS Lambda follows [AWS Lambda Runtime deprecation policy cycle](https://docs.aws.amazon.com/lambda/latest/dg/lambda-runtimes.html#runtime-support-policy), when it comes to Language Runtime. This means we will stop supporting deprecated Language Runtime without increasing the major SDK version. +Powertools for AWS Lambda follows the [AWS Lambda Runtime deprecation policy cycle](https://docs.aws.amazon.com/lambda/latest/dg/lambda-runtimes.html#runtime-support-policy), when it comes to Language Runtime. This means we will stop supporting deprecated their respective Language Runtime without increasing the major SDK version. !!! note "AWS reserves the right to stop support for an underlying dependency without increasing the major SDK version" From 891329d31dceb497dd1404651add2c64be1eaa98 Mon Sep 17 00:00:00 2001 From: Leandro Damascena Date: Tue, 30 Jan 2024 15:56:42 +0000 Subject: [PATCH 5/7] Adressing Andrea's feedback --- docs/versioning.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/versioning.md b/docs/versioning.md index 55bef7c0111..58a8ba235ba 100644 --- a/docs/versioning.md +++ b/docs/versioning.md @@ -39,7 +39,7 @@ The following terms are used to classify underlying third party dependencies: * [**AWS Lambda Runtime**](https://docs.aws.amazon.com/lambda/latest/dg/lambda-runtimes.html): Examples include `nodejs20.x`, `python3.12`, etc. * **Language Runtime**: Examples include Python 3.12, NodeJS 20, Java 17, .NET Core, etc. -* **Third party Library**: Examples include Pydantic, AWS X-Ray SDK, AWS Encryption SDK, MiddyJS, etc. +* **Third party Library**: Examples include Pydantic, AWS X-Ray SDK, AWS Encryption SDK, Middy.js, etc. Powertools for AWS Lambda follows the [AWS Lambda Runtime deprecation policy cycle](https://docs.aws.amazon.com/lambda/latest/dg/lambda-runtimes.html#runtime-support-policy), when it comes to Language Runtime. This means we will stop supporting deprecated their respective Language Runtime without increasing the major SDK version. From c0fecf3c6a3a054f9c6f7ace5039fdc6f5c6fb13 Mon Sep 17 00:00:00 2001 From: heitorlessa Date: Wed, 31 Jan 2024 10:26:41 +0100 Subject: [PATCH 6/7] docs: GA minimal commitment adjustment to allow each language to set their baseline --- docs/versioning.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/versioning.md b/docs/versioning.md index 58a8ba235ba..79d2dcf7ec9 100644 --- a/docs/versioning.md +++ b/docs/versioning.md @@ -22,7 +22,7 @@ Powertools for AWS Lambda release versions are in the form of X.Y.Z where X repr The lifecycle for major Powertools for AWS Lambda versions consists of 5 phases, which are outlined below. * **Developer Preview** (Phase 0) - During this phase, SDKs are not supported, should not be used in production environments, and are meant for early access and feedback purposes only. It is possible for future releases to introduce breaking changes. Once AWS identifies a release to be a stable product, it may mark it as a Release Candidate. Release Candidates are ready for GA release unless significant bugs emerge, and will receive full AWS support. -* **General Availability (GA)** (Phase 1) - During this phase, SDKs are fully supported. AWS will provide regular SDK releases that include support for new features, enhancements, as well as bug and security fixes. AWS will support the GA version of an SDK for _at least 24 months_. +* **General Availability (GA)** (Phase 1) - During this phase, SDKs are fully supported. AWS will provide regular SDK releases that include support for new features, enhancements, as well as bug and security fixes. AWS will support the GA version of an SDK for _at least 24 months_, unless otherwise specified. * **Maintenance Announcement** (Phase 2) - AWS will make a public announcement at least 6 months before an SDK enters maintenance mode. During this period, the SDK will continue to be fully supported. Typically, maintenance mode is announced at the same time as the next major version is transitioned to GA. * **Maintenance** (Phase 3) - During the maintenance mode, AWS limits SDK releases to address critical bug fixes and security issues only. An SDK will not receive API updates for new or existing services, or be updated to support new regions. Maintenance mode has a _default duration of 6 months_, unless otherwise specified. * **End-of-Support** (Phase 4) - When an SDK reaches end-of support, it will no longer receive updates or releases. Previously published releases will continue to be available via public package managers and the code will remain on GitHub. The GitHub repository may be archived. Use of an SDK which has reached end-of-support is done at the user’s discretion. We recommend users upgrade to the new major version. From 46ea32e3934723dbeff7e251e04e5e31ad82fa05 Mon Sep 17 00:00:00 2001 From: heitorlessa Date: Wed, 31 Jan 2024 10:30:10 +0100 Subject: [PATCH 7/7] docs: final line editing --- docs/versioning.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/versioning.md b/docs/versioning.md index 79d2dcf7ec9..44349f4bfc2 100644 --- a/docs/versioning.md +++ b/docs/versioning.md @@ -41,7 +41,7 @@ The following terms are used to classify underlying third party dependencies: * **Language Runtime**: Examples include Python 3.12, NodeJS 20, Java 17, .NET Core, etc. * **Third party Library**: Examples include Pydantic, AWS X-Ray SDK, AWS Encryption SDK, Middy.js, etc. -Powertools for AWS Lambda follows the [AWS Lambda Runtime deprecation policy cycle](https://docs.aws.amazon.com/lambda/latest/dg/lambda-runtimes.html#runtime-support-policy), when it comes to Language Runtime. This means we will stop supporting deprecated their respective Language Runtime without increasing the major SDK version. +Powertools for AWS Lambda follows the [AWS Lambda Runtime deprecation policy cycle](https://docs.aws.amazon.com/lambda/latest/dg/lambda-runtimes.html#runtime-support-policy), when it comes to Language Runtime. This means we will stop supporting their respective deprecated Language Runtime _(e.g., `python37`)_ without increasing the major SDK version. !!! note "AWS reserves the right to stop support for an underlying dependency without increasing the major SDK version"