Release dashboard: skip pre-pre-release versions with no branch yet#669
Closed
hugovk wants to merge 1 commit intopython:mainfrom
Closed
Release dashboard: skip pre-pre-release versions with no branch yet#669hugovk wants to merge 1 commit intopython:mainfrom
hugovk wants to merge 1 commit intopython:mainfrom
Conversation
Member
Author
Member
|
Would you be OK with just de-emphasizing it? |
Member
|
See #671 :) |
Member
Author
|
Closing in favour of #671. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

3.16 hasn't started development yet but https://buildbot.python.org/#/release_status shows it:
This will be because the 3.16 schedule PEP has been merged (python/peps#4829) and we now generate the release PEPs from a single-source-of-truth TOML in the PEPs repo: https://github.com/python/peps/blob/main/release_management/python-releases.toml
We also generate https://peps.python.org/api/release-cycle.json from this, which includes:
{ "3.16": { "branch": "", "pep": 826, "status": "", "first_release": "2027-10-06", "end_of_life": "2032-10", "release_manager": "Savannah Ostrowski" }, "3.15": { "branch": "main", "pep": 790, "status": "feature", "first_release": "2026-10-01", "end_of_life": "2031-10", "release_manager": "Hugo van Kemenade" }, ...And that JSON is used for the release dashboard.
Let's skip versions with no branch set.
Note: I've not tested this fix locally or otherwise.