Rooba
/
tornado
mirror of https://github.com/tornadoweb/tornado.git
1
1
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Updated Release instructions (markdown)

A. Jesse Jiryu Davis 2016-09-30 20:36:59 -04:00
parent 3fff251226
commit a32ac7fed9
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
Release-instructions.md

@ -14,9 +14,9 @@
1. Build the release tarball: `python setup.py sdist` (The tarball goes in `dist/tornado-X.Y.tar.gz`) 1. Build the release tarball: `python setup.py sdist` (The tarball goes in `dist/tornado-X.Y.tar.gz`)
1. Test the release tarball in an isolated environment: `virtualenv /tmp/test_env; /tmp/test_env/bin/pip install path/to/tornado-X.Y.tar.gz; /tmp/test_env/bin/python -m tornado.test` 1. Test the release tarball in an isolated environment: `virtualenv /tmp/test_env; /tmp/test_env/bin/pip install path/to/tornado-X.Y.tar.gz; /tmp/test_env/bin/python -m tornado.test`
1. Push the tag to github: `git push origin vX.Y.Z`. Also push all updated branches. 1. Push the tag to github: `git push origin vX.Y.Z`. Also push all updated branches.
1. This triggers a Windows binary build on `appveyor.com`. Download the resulting artifacts (click on the tag build, and for each of the 32- and 64-bit environments click on the artifacts tab and download the `.whl` file). TODO: automate this. Also consider building the source tarball and mac binaries on travis-ci. 1. This triggers a Windows binary build on `appveyor.com`. [Download the resulting artifacts](https://ci.appveyor.com/project/bdarnell/tornado) (click on the tag build, and for each of the 32- and 64-bit environments click on the artifacts tab and download the `.whl` file). TODO: automate this. Also consider building the source tarball and mac binaries on travis-ci.
1. Upload the releases: `twine upload dist/tornado-X.Y.tar.gz; twine upload downloads/tornado-X.Y.*.whl` 1. Upload the releases: `twine upload dist/tornado-X.Y.Z.tar.gz; twine upload downloads/tornado-X.Y.Z-*.whl`
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. 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. 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.
1. Announce on [python-tornado](https://groups.google.com/forum/#!forum/python-tornado) and [python-tornado-announce](https://groups.google.com/forum/#!forum/python-tornado-announce) mailing lists.