Skip to content

docs: add v2 -> v3 version lifecycle table to README#5979

Merged
jam-jee merged 1 commit into
aws:master-v2from
jam-jee:docs/v2-lifecycle-table
Jul 1, 2026
Merged

docs: add v2 -> v3 version lifecycle table to README#5979
jam-jee merged 1 commit into
aws:master-v2from
jam-jee:docs/v2-lifecycle-table

Conversation

@jam-jee

@jam-jee jam-jee commented Jun 30, 2026

Copy link
Copy Markdown
Collaborator

Issue #, if available: N/A

Description of changes:

Adds a Version Lifecycle section to the v2 README documenting the SageMaker Python SDK lifecycle per the AWS SDKs and Tools maintenance policy.

The section states that v3 is GA (2025-11-19) and the actively developed major version, that v2 is in maintenance mode (critical bug fixes + security only), and includes:

  • a Phase / Start Date / End Date table (General Availability, Maintenance mode, End-of-Support) modeled on the AWS SDK for Java v1 lifecycle table,
  • per-phase support definitions taken from the policy,
  • the migration-guide link, and
  • pip install "sagemaker<3" (pin) / pip install --upgrade sagemaker (upgrade) commands.

Also adds a Table of Contents entry. Dates were aligned with the product team following the policy (maintenance announcement anchored to v3 GA; +6 months to maintenance, +12 months to end-of-support). v2.0.0 GA date (2020-08-04) confirmed from PyPI.

This complements the runtime deprecation-warning work in #5978 (the policy lists both updated docs and in-SDK deprecation warnings as required communication channels).

Testing done:

Docs-only change. Validated that README.rst parses cleanly with docutils (no RST errors; simple-table columns align). No code changed.

Merge Checklist

  • I have read the CONTRIBUTING doc
  • I certify that the changes I am introducing will be backward compatible (documentation only; no code or API change)
  • I used the commit message format described in CONTRIBUTING
  • I have updated any necessary documentation (this PR is the documentation update)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@jam-jee jam-jee requested a review from a team as a code owner June 30, 2026 17:50
@jam-jee jam-jee requested a review from zhaoqizqwang June 30, 2026 17:50
@jam-jee jam-jee force-pushed the docs/v2-lifecycle-table branch from 8bac670 to c048dbd Compare June 30, 2026 23:32
Document the SageMaker Python SDK version lifecycle per the AWS SDKs and
Tools maintenance policy. Adds a "Version Lifecycle" section (and a Table
of Contents entry) to the v2 README stating that v3 is GA (2025-11-19) and
the actively developed major version, and that v2 is in maintenance mode.

Includes a Phase / Start Date / End Date table (GA, Maintenance mode,
End-of-Support) modeled on the AWS SDK for Java v1 lifecycle table, the
per-phase support definitions, the migration-guide link, and the v2-pin /
v3-upgrade pip commands. Dates aligned with product: maintenance mode
2026-07-06 to 2027-07-05 (12 months), end-of-support 2027-07-06.
@jam-jee jam-jee force-pushed the docs/v2-lifecycle-table branch from c048dbd to ea32246 Compare June 30, 2026 23:35
@jam-jee jam-jee merged commit 6a1bed9 into aws:master-v2 Jul 1, 2026
8 of 11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants