= Deluge Release Checklist = == Pre-Release == * Compress WebUI javascript (from `deluge/ui/web/`) * `./build js/deluge-all` * `./build js/ext-extensions` * Update WebUI `gettext.js` (from `deluge/ui/web/`) * `./gen_gettext.py` * Update [wiki:Development/Translation translation] `po` files from [https://translations.launchpad.net/deluge Launchpad] * Changelog is updated with relevant commits and release date is added. * Version number increment: * setup.py * man pages * osx/Info.plist ''e.g.'' Version: `git grep -l '1\.3\.10' | grep -v ChangeLog | xargs sed -i 's/1\.3\.10/1\.3\.11/g'`[[br]] ''e.g.'' Month: `git grep -l 'October' docs/man | xargs sed -i 's/October/November/g'` * Increment copyright year: * about_dialog.py * osx/Info.plist * Tag release in git and push upstream. * e.g. `git tag -a deluge-1.3.11 -m "Deluge 1.3.11 Release"` == Release == * Use git archive to create initial tarball ''e.g.'' * `git archive --format=tar --prefix=deluge-1.3.11/ deluge-1.3.11 >deluge-1.3.11.tar ` * Run `make_release` script on extracted tarball ''e.g.'' * `make_release deluge-1.3.0` == Post-Release == * Update with version, hashes and release notes: * ReleaseNotes (Create new version page and add link to this page) * Forum Announcement * IRC Welcome Message * Website `index.php` and `version` files * [http://en.wikipedia.org/wiki/Deluge_%28software%29 Wikipedia] * Trac close the milestone and add new version for tickets. * Ensure all stable branch commits are also applied to development branch.