iSharkFly-Open
/
python-peps
mirror of https://github.com/python/peps.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

[pep-101] Remove outdated mentions of editing 'Pages' in the pydotorg admin

This commit is contained in:
Łukasz Langa 2019-02-03 19:10:28 +01:00
parent 9528786fa7
commit a02575901a
No known key found for this signature in database
GPG Key ID: B26995E310250568
1 changed files with 10 additions and 39 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

49
pep-0101.txt
View File

@ -513,57 +513,28 @@ to perform some manual editing steps.
To ensure that the regression test suite passes. If not, you
screwed up somewhere!
Now it's time to twiddle the web site.
Now it's time to twiddle the web site. None of this is automated by release.py
at the moment, sorry.
To do these steps, you must have the permission to edit the website. If you
don't have that, ask someone on pydotorg@python.org for the proper
permissions. (Or ask Ewa, who coordinated the effort for the new newbsite
with RevSys.)
XXX This is completely out of date for Django-based python.org.
This page will probably come in handy:
http://docutils.sourceforge.net/docs/user/rst/quickref.html
None of the web site updates are automated by release.py.
- Log in to http://www.python.org/admin .
- If this is the first release for this version (even a new patch
version), you'll need to create a "page" for the version.
Find the "Pages" section and click on "Add", then fill in the
form.
Note that the easiest thing is probably to copy fields from
an existing Python release "page", editing as you go.
There should only be one "page" for a release (e.g. 3.5.0, 3.5.1).
Reuse the same page for all pre-releases, changing the version
number and the documentation as you go.
- If this isn't the first release for a version, open the existing
"page" for editing and update it to the new release. Don't save yet!
- Now create a new "release" for the release. Currently "Releases" are
- Create a new "release" for the release. Currently "Releases" are
sorted under "Downloads".
Again, the easiest thing is probably to copy fields from
an existing Python release "page", editing as you go.
The easiest thing is probably to copy fields from an existing
Python release "page", editing as you go.
The mysterious "Release page" field on the form needs the
ID number of the "page" for this version. You can get that
by examining the URL for the "change page" form for this
version. For example, the URL for editing the "page"
for Python 3.5 is:
You can use `Markdown <https://daringfireball.net/projects/markdown/syntax>`_ or
`ReStructured Text <http://docutils.sourceforge.net/docs/user/rst/quickref.html>`_
to describe your release. The former is less verbose, while the latter has nifty
integration for things like referencing PEPs.
https://www.python.org/admin/pages/page/1232/
The page's ID number is the last field; here it is 1232.
- Note that by convention, the "Content" on the page and
the "Content" on the release are the same, *except* the
"page" has a section on where to download the software.
Leave the mysterious "Release page" field on the form empty.
- "Save" the release.