[Docs] Updates to release checklist

docs/source/devguide/packaging/release.md

@@ -4,6 +4,7 @@
 
 - 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"
@@ -18,7 +19,6 @@
 
       twine upload dist/deluge-2.0.0.tar.gz dist/deluge-2.0.0-py3-none-any.whl
 
-- Create packages (Ubuntu, Windows, OSX).
 - Calculate `sha256sum` for each file e.g.
 
       cd dist; sha256sum deluge-2.0.0.tar.xz > deluge-2.0.0.tar.xz.sha256
@@ -27,16 +27,17 @@
   - 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`.
-- Update latest release version in `version` files at `download.deluge-torrent.org`.
+  - 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].
-  - ReleaseNotes (Create new version page and add link to this page)
-  - Forum announcement
-  - IRC welcome message
-  - Website homepage version `/var/www/deluge-torrent.org/htdocs/index.php`
+  - 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.
@@ -44,4 +45,5 @@
 [readthedocs]: https://deluge.readthedocs.io
 [wikipedia]: http://en.wikipedia.org/wiki/Deluge_%28software%29
 [launchpad]: https://translations.launchpad.net/deluge
-[translation]: ../contributing/translations.md
+[translation]: ../../contributing/translations.md
+[release notes]: ../../release/index.md