deluge/docs/source/devguide/packaging/release.md

50 lines
1.6 KiB
Markdown

# Release Checklist
## Pre-release
- Update [translation] `po` files from [Launchpad] account.
- Changelog is updated with relevant commits and release date is added.
- Docs [release notes] are updated.
- Tag release in git and push upstream e.g.
git tag -a deluge-2.0.0 -m "Deluge 2.0.0 Release"
## Release
- Create source and wheel distributions:
python setup.py sdist bdist_wheel
- Upload to PyPi (currently only accepts `tar.gz`):
twine upload dist/deluge-2.0.0.tar.gz dist/deluge-2.0.0-py3-none-any.whl
- Calculate `sha256sum` for each file e.g.
cd dist; sha256sum deluge-2.0.0.tar.xz > deluge-2.0.0.tar.xz.sha256
- Upload source tarballs and packages to `download.deluge-torrent.org`.
- Ensure file permissions are global readable: `0644`
- Sub-directories correspond to _major.minor_ version e.g. all `2.0.x` patch
releases are stored in `source/2.0`.
- Change release version in `version` files.
- Run `trigger-deluge` to sync OSUOSL FTP site.
- Create packages (Ubuntu, Windows, OSX).
- Ubuntu: <https://code.launchpad.net/~deluge-team/+recipe/stable-releases>
## Post-release
- Update with version, hashes and release notes:
- Publish docs on [ReadTheDocs].
- Forum announcement.
- IRC welcome message.
- [Wikipedia]
- Close Trac milestone and add new milestone version for future tickets.
- Ensure all stable branch commits are also applied to development branch.
[readthedocs]: https://deluge.readthedocs.io
[wikipedia]: http://en.wikipedia.org/wiki/Deluge_%28software%29
[launchpad]: https://translations.launchpad.net/deluge
[translation]: ../../contributing/translations.md
[release notes]: ../../release/index.md