Updated Release instructions (markdown)
parent
9424ee3092
commit
159ac47225
|
@ -19,3 +19,4 @@
|
||||||
1. If this release creates a new `branchX.Y`, go to `readthedocs.org` and enable builds for that branch.
|
1. If this release creates a new `branchX.Y`, go to `readthedocs.org` and enable builds for that branch.
|
||||||
1. Announce on `python-tornado` and `python-tornado-announce` mailing lists.
|
1. Announce on `python-tornado` and `python-tornado-announce` mailing lists.
|
||||||
1. Update the version number on the master branch. In between releases the version number has a `.dev1` suffix (or occasionally `.dev2`, etc, if we want to mark particular milestones in the in-development version): release `4.4.0` is followed by version `4.5.0.dev1`.
|
1. Update the version number on the master branch. In between releases the version number has a `.dev1` suffix (or occasionally `.dev2`, etc, if we want to mark particular milestones in the in-development version): release `4.4.0` is followed by version `4.5.0.dev1`.
|
||||||
|
1. On [pypi](https://pypi.python.org/pypi?:action=pkg_edit&name=tornado), mark all but the latest release as "hidden". This is not automated so that beta releases don't hide the latest non-beta release.
|
Loading…
Reference in New Issue