Thanks to visit codestin.com
Credit goes to github.com

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
Closed
Show file tree
Hide file tree
Changes from all commits
Commits
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
2 changes: 1 addition & 1 deletion docs/source/administration.rst
Original file line number Diff line number Diff line change
Expand Up @@ -65,7 +65,7 @@ Downloads and Releases
The ``downloads`` app stores all of the structured data regarding Python releases. Each ``Release`` object has associated ``ReleaseFile`` objects that contain information on the various download formats Python.org
supports.

If the version you are creating should be considered the "latest" release for the major version in question (Python 2.x.x, 3.x.x, etc)
If the version you are creating should be considered the "latest" release for the minor version in question (Python 2.x.x, 3.x.x, etc)
then check the 'Is this the latest release' checkbox. When the ``Release`` is saved, the previous version will be automatically
demoted for you and the new version will be used prominently on the site. For example the download buttons and supernav links.

Expand Down
Loading