PEP 101: Added hint on how to add a Python Insider blog post for new releases.
This commit is contained in:
parent
bb09381e29
commit
e23887d494
|
@ -410,7 +410,7 @@ How to Make A Release
|
|||
Make sure they are world readable. They should also be group
|
||||
writable, and group-owned by downloads.
|
||||
|
||||
___ Use `gpg --verify` to make sure they got uploaded intact.
|
||||
___ Use ``gpg --verify`` to make sure they got uploaded intact.
|
||||
|
||||
___ If this is a final release: Move the doc zips and tarballs to
|
||||
/srv/www.python.org/ftp/python/doc/X.Y.Z, creating the directory
|
||||
|
@ -547,7 +547,9 @@ How to Make A Release
|
|||
python-announce@python.org
|
||||
python-dev@python.org
|
||||
|
||||
___ Also post the announcement to <http://blog.python.org>.
|
||||
___ Also post the announcement to `The Python Insider blog
|
||||
<http://blog.python.org>`_. To add a new entry, go to
|
||||
`your Blogger home page, here. <https://www.blogger.com/home>`_
|
||||
|
||||
Now it's time to do some cleaning up. These steps are very important!
|
||||
|
||||
|
|
Loading…
Reference in New Issue