Skip to content

3.11 documentation has no changelog entry for 3.11.9 #121484

Closed

Description

@sparrowt

Documentation

As listed on https://www.python.org/downloads/ the latest release of 3.11 is 3.11.9

However on the changelog for 3.11 the latest release is 3.11.8 ⚠️
https://docs.python.org/3.11/whatsnew/changelog.html

Comparing with 3.12 where the latest release is 3.12.4, as expected the 3.12 changelog has 3.12.4 ✔️
https://docs.python.org/3.12/whatsnew/changelog.html

Is this a documentation bug that 3.11.9 isn't listed on the 3.11 changelog?

In fact all of the documentation when on the 3.11 section says 3.11.8 in the title etc e.g. https://docs.python.org/3.11/index.html

Activity

  1. Eclips4 commented on Jul 8, 2024

    @Eclips4
    Member
  2. hugovk commented on Jul 8, 2024

    @hugovk
    Member

    See python/docsbuild-scripts#169 (comment), docs for security branches need to be built manually.

    And see also #113726 about 3.8 and 3.9.

    I think we're missing something in the process here.

    What is the process for rebuilding docs when we make security releases? Where is this (or where should it be) documented? PEP 101?

    cc @JulienPalard

  3. pablogsal commented on Jul 13, 2024

    @pablogsal
    Member

    @ambv you know if we are missing something? This was handled correctly for 3.10 automatically IIRC

  4. ambv commented on Jul 13, 2024

    @ambv
    Contributor

    We haven't built the docs automatically for sec branches ever.

  5. sparrowt commented on Sep 4, 2024

    @sparrowt
    ContributorAuthor

    Ok thanks for looking into it - it does seem to be a missing step in some process and is still showing 3.11.8 for me.

  6. ambv commented on Sep 4, 2024

    @ambv
    Contributor

    We will rebuild all docs for old versions late this week once the new security versions are released.

  7. ambv commented on Sep 10, 2024

    @ambv
    Contributor

    https://docs.python.org/3.11/ now points at 3.11.10.

  8. sparrowt commented on Dec 5, 2024

    @sparrowt
    ContributorAuthor

    FYI the same has happened for 3.11.11, 3.10.16 and 3.9.21 which are all missing from the 3.11/3.10/3.9 changelog pages (whereas 3.12.8 and 3.13.1 are correctly shown on the 3.12/3.13 changelog pages) - all 5 were released on the same day.

    Perhaps this is normal 2 days after the release, but just flagging it in case it isn't. Thanks everyone!

    https://docs.python.org/3.13/whatsnew/changelog.html#python-3-13-1-final ✅
    https://docs.python.org/3.12/whatsnew/changelog.html#python-3-12-8-final ✅
    https://docs.python.org/3.11/whatsnew/changelog.html missing latest
    https://docs.python.org/3.10/whatsnew/changelog.html missing latest
    https://docs.python.org/3.9/whatsnew/changelog.html missing latest

  9. hugovk commented on Dec 7, 2024

    @hugovk
    Member

    Security branches need manual builds and it takes ~16 hours for a full build (all languages and all formats -- HTML, PDF, etc).

    3.11 is now done, 3.10 has begun: python/docsbuild-scripts#216 (comment)

    Tip: you can also check the version in the title and the timestamp in the footer of the homepage: for example, https://docs.python.org/3.10/ still on 3.10.15 and "Last updated on Sep 09, 2024".

  10. hugovk commented on Dec 9, 2024

    @hugovk
    Member

    3.9-3.11 are now rebuilt:

    • 3.11: 2024-12-07 11:37:08,426 INFO: Full build done (16h 18m 2s).
    • 3.10: 2024-12-08 00:38:35,718 INFO: Full build done (12h 49m 46s).
    • 3.9: 2024-12-09 09:35:58,914 INFO: Full build done (15h 18m 37s).

    Thanks for the reminder!

  11. sparrowt commented on Dec 10, 2024

    @sparrowt
    ContributorAuthor

    Thanks! I wonder if there's some checklist (or nag bot) that could be updated so that the process is more future-proof?

  12. hugovk commented on Dec 16, 2024

    @hugovk
    Member

    Yes, this was partly a bus factor issue, afaik it used to be just one person had access or knew how to do manually rebuilds.

    I've now documented what's needed at https://github.com/python/docsbuild-scripts#manually-rebuild-a-branch, and two people plus four release managers have access to redo them. I'll tell the other RMs about this (although 3/4 are already in this issue :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    3.11only security fixesdocsDocumentation in the Doc dir

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions