8000 PEP 101: Simplified due to centralisation of switchers in the doc. by JulienPalard · Pull Request #1438 · python/peps · GitHub
[go: up one dir, main page]
Skip to content

PEP 101: Simplified due to centralisation of switchers in the doc. #1438

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.

Sign up for GitHub

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

Merged
merged 7 commits into from
Nov 7, 2020
Merged

PEP 101: Simplified due to centralisation of switchers in the doc. #1438

Changes from 1 commit
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
d5f8793
Doing Python Releases 101: Simplified due to centralisation of langua…
JulienPalard Jun 18, 2020
8b69297
backslash not needed.
JulienPalard Jun 22, 2020
d8c0578
FIX: Missing backslash.
JulienPalard Jun 22, 2020
abf05b2
consistency
JulienPalard Jun 22, 2020
ad4cd7a
Factor 3 links.
JulienPalard Jun 22, 2020
82ae4b2
FIX: Ugly apostrophes after [1].
JulienPalard Jun 22, 2020
24784f9
Missing
JulienPalard Nov 7, 2020
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
Prev Previous commit
Next Next commit
FIX: Ugly apostrophes after [1].
  • Loading branch information
@JulienPalard
JulienPalard committed Nov 7, 2020
commit 82ae4b22bc09c3977997296fbc8a922241bb2afe
10 changes: 5 additions & 5 deletions pep-0101.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -305,12 +305,12 @@ to perform some manual editing steps.
release tag in the repo is signed with your gpg key. When prompted
choose the private key you use for signing release tarballs etc.

- For a **new branch** release, add it to `docsbuild scripts`_'
``VERSIONS`` list, so that the new maintenance branch is now
- For a **new branch** release, add it to the ``VERSIONS`` list of
`docsbuild scripts`_, so that the new maintenance branch is now
``pre-release`` and add the new ``in development`` version.

- For a **final** major release, `docsbuild scripts`_' ``VERSIONS``
list must be updated, changing the release branch from
- For a **final** major release, update the ``VERSIONS`` list of
`docsbuild scripts`_: the release branch must be changed from
``pre-release`` to ``stable``, tell the DE to update the ``/3/``
symlink.

Expand Down Expand Up @@ -879,7 +879,7 @@ else does them. Some of those tasks include:
- Optionally making a final release to publish any remaining unreleased
changes.

- Update `docsbuild scripts`_' ``VERSIONS`` list, changing the
- Update the ``VERSIONS`` list of `docsbuild scripts`_: change the
version state to ``EOL``.

- On the docs download server (docs.nyc1.psf.io), ensure the top-level
Expand Down
0