From 159ac47225f6ee95edb877c5b57a2deeb52a4ede Mon Sep 17 00:00:00 2001 From: Ben Darnell Date: Sat, 23 Jul 2016 13:21:18 -0400 Subject: [PATCH] Updated Release instructions (markdown) --- Release-instructions.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/Release-instructions.md b/Release-instructions.md index cdce6fe..a40ab49 100644 --- a/Release-instructions.md +++ b/Release-instructions.md @@ -18,4 +18,5 @@ 1. Upload the releases: `twine upload dist/tornado-X.Y.tar.gz; twine upload downloads/tornado-X.Y.*.whl` 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. 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`. \ No newline at end of file +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. \ No newline at end of file