pofiles 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"
Create source and wheel distributions:
python setup.py sdist bdist_wheel
Upload to PyPi (only accepts
twine upload dist/deluge-2.0.0.tar.gz dist/deluge-2.0.0-py3-none-any.whl
sha256sumfor 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
Ensure file permissions are global readable:
Sub-directories correspond to major.minor version e.g. all
2.0.xpatch releases are stored in
Change release version in
version*files, create a new version file for any major releases.
SSH into OSUOSL FTP site and run
trigger-delugeto sync files.
Create packages (Ubuntu, Windows, OSX).
Ensure launchpad git repo has sync’d to get latest version
Update version in recipe (reset any dash number to 0)
Check for new distribution series needing selected.
Request build for selected series.
Update with version, hashes and release notes:
Publish new docs version on ReadTheDocs.
Close Trac milestone and add new milestone version for future tickets.
Ensure all stable branch commits are also applied to development branch.