Skip to content

Clarify documentation backports in release status key #1945

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

Open
badrisatyam1-ctrl wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Clarify documentation backports in release status key #1945

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
b090661
docs: clarify documentation backports
badrisatyam1-ctrl Oct 27, 2026
9f7471d
Merge branch 'main' into codex/document-backport-policy
badrisatyam1-ctrl Oct 28, 2026
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
17 changes: 9 additions & 8 deletions versions.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -54,19 +54,20 @@ Python releases go through five phases, as described in :pep:`602`. Release
managers can adjust specific dates as needed.

:feature: Before the first beta, the next full release can accept new features,
bug fixes, and security fixes.
bug fixes, documentation changes, and security fixes.

:prerelease: After the first beta, no new features can go in, but feature fixes
(including significant changes to new features), bug fixes, and security fixes
are accepted for the upcoming feature release.
(including significant changes to new features), bug fixes, documentation
changes, and security fixes are accepted for the upcoming feature release.

:bugfix: Once a version has been fully released, bug fixes and security fixes are
accepted. New binaries are built and released roughly every two months. This
phase is also called **maintenance** mode or **stable** release.
:bugfix: Once a version has been fully released, bug fixes, documentation
changes, and security fixes are accepted. New binaries are built and released
roughly every two months. This phase is also called **maintenance** mode or
**stable** release.

:security: After two years (18 months for versions before 3.13), only security
fixes are accepted and no more binaries are released. New source-only versions
can be released as needed.
fixes and security-related documentation changes are accepted, and no more
binaries are released. New source-only versions can be released as needed.

:end-of-life: Five years after a release, support ends. The release cycle is
frozen; no further changes are allowed.
Expand Down