Skip to content

don't denote old versions as 'the newest major release of Python' #2284

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.

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

Closed
wants to merge 5 commits into from

Conversation

erlend-aasland
Copy link

@erlend-aasland
Copy link
Author

erlend-aasland commented Jun 16, 2023

I was unable to find out where the "is the newest major release of the Python programming language" string for 3.11.x was located (but I did not devote much time for the investigation either ...):

https://www.python.org/downloads/release/python-3114/

For 3.11.4, it is true that it's the newest major release of Python, but that's not true for 3.11.3 and older. Perhaps "the newest stable release of Python" is more accurate.

@erlend-aasland
Copy link
Author

(I reverted 252ddbd as it broke CI, and I have no time to investigate that)

@jamestwebber
Copy link

I was unable to find out where the "is the newest major release of the Python programming language" string for 3.11.x was located (but I did not devote much time for the investigation either ...):

It seems like these are only present in the fixtures/downloads.json file, which I think means it is stored in the database as markdown and just gets rendered in its entirety? So possibly someone (the release manager?) is writing this by hand (or has a template they use for it)

@erlend-aasland
Copy link
Author

Yep, makes sense.

@ewdurbin
Copy link
Member

The changes here are for the fixtures. The contents itself is managed in the CMS in the live database.

Happy to merge, but it will have no impact on the live pages at python.org. Someone from @python/python-release-managers will need to update the existing CMS contents.

@erlend-aasland
Copy link
Author

If it has no impact, there's no need to merge :) Thanks for the info!

@erlend-aasland erlend-aasland deleted the versioning branch July 20, 2023 19:23
@jamestwebber
Copy link

The change to docs/source/administration.rst is still relevant, yes? It's a tiny point but perhaps would help nudge future announcements to use precise wording.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants