Skip to content

Conversation

@m-aciek
Copy link
Contributor

@m-aciek m-aciek commented Nov 10, 2025

Feature freeze date is used to be point of docs translations start for a release (at least for those using translation platform). Having the date would allow to base the automations on release-cycle.json file.


📚 Documentation preview 📚: https://pep-previews--4698.org.readthedocs.build/

@m-aciek m-aciek requested a review from a team as a code owner November 10, 2025 21:21
@hugovk
Copy link
Member

hugovk commented Nov 10, 2025

Feature freeze is defined as beta 1, which is already exposed in the full https://peps.python.org/api/pythonreleases.json

For example:

      {
        "stage": "3.15.0 beta 1",
        "state": "expected",
        "date": "2026-05-05",
        "note": ""
      },

Can you use this instead?

@hugovk hugovk added the infra Core infrastructure for building and rendering PEPs label Nov 10, 2025
@m-aciek
Copy link
Contributor Author

m-aciek commented Nov 10, 2025

It's accessible even easier, in the metadata part:

    "3.15": {
      "pep": 790,
      "status": "feature",
      "branch": "main",
      "release_manager": "Hugo van Kemenade",
      "start_of_development": "2025-05-07",
      "feature_freeze": "2026-05-05",
      "first_release": "2026-10-01",
      "end_of_bugfix": "2028-10-01",
      "end_of_life": "2031-10-01"
    }

Thank you for the pointer.

@m-aciek m-aciek closed this Nov 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

infra Core infrastructure for building and rendering PEPs

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants