Skip to content

PEP 101: Instruct the Release Manager to change python-releases.toml #4697

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
wants to merge 2 commits into
base: main
Choose a base branch
from
+6 −6
Open

PEP 101: Instruct the Release Manager to change python-releases.toml #4697

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
bb06556
PEP 101: Instruct the Release Manager to change ``python-releases.toml``
AA-Turner Nov 10, 2025
c64d0a6
fixup
AA-Turner Nov 10, 2025
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
12 changes: 6 additions & 6 deletions peps/pep-0101.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -726,8 +726,7 @@ permissions.
- Update the `issue tracker`_ for the new branch:
add the new version to the versions list.

- Update the `devguide
<https://github.com/python/devguide/blob/main/include/release-cycle.json>`__
- Update `python-releases.toml <../release_management/python-releases.toml>`__
Copy link
Member

@hugovk hugovk Nov 10, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This relative link doesn't work:

Copy link
Member Author

@AA-Turner AA-Turner Nov 10, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This makes a relative link on the web (e.g. https://pep-previews--4697.org.readthedocs.build/release_management/python-releases.toml), which isn't what we want. Best to remove the link, or just to link to GH instead?

Copy link
Member Author

@AA-Turner AA-Turner Nov 10, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@hugovk snap again :)

What do you think of either of the above suggestions?

Copy link
Member

@hugovk hugovk Nov 10, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

:)

Yeah, let's link to GH instead: https://github.com/python/peps/blob/main/release_management/python-releases.toml

to reflect the new branches and versions.

- Create a PR to update the supported releases table on the
Expand Down Expand Up @@ -812,10 +811,11 @@ else does them. Some of those tasks include:

* https://www.python.org/downloads/release/python-336/

- In the `developer's guide
<https://github.com/python/devguide/blob/main/include/release-cycle.json>`__,
set the branch status to end-of-life
and update or remove references to the branch elsewhere in the devguide.
- In `python-releases.toml <../release_management/python-releases.toml>`__,
set the branch status to end-of-life.

- Update or remove references to the branch in the `developer's guide
<https://github.com/python/devguide/>`__.

- Retire the release from the `issue tracker`_. Tasks include:

Expand Down