Difference between revisions of "Release Checklist"

From Mudlet
Jump to navigation Jump to search
(+link to international news manual)
m (+link to international news manual)
Line 20: Line 20:
 
## ☐ close github milestone
 
## ☐ close github milestone
 
## ☐ [[Howto:Update Downloads|update downloads on mudlet.org]]
 
## ☐ [[Howto:Update Downloads|update downloads on mudlet.org]]
## ☐ post news on mudlet.org - [for https://github.com/Mudlet/Mudlet/issues/2550 all languages]
+
## ☐ post news on mudlet.org - [https://github.com/Mudlet/Mudlet/issues/2550 for all languages]
 
## ☐ Create Quick Redirect like mudlet.org/3-23
 
## ☐ Create Quick Redirect like mudlet.org/3-23
 
## ☐ post news to https://launchpad.net/mudlet
 
## ☐ post news to https://launchpad.net/mudlet

Revision as of 19:57, 5 June 2019

Mudlet release checklist

  1. 5 days before the release
    1. ☐ update mudlet.ts with the latest translations strings for translators to translate (using Q 5.12.2+ lupdate ./src/ -ts ./translations/mudlet.ts), NB the -recursive option is not needed as it is the default option.
    2. ☐ update mudlet_en_US.ts with the latest translation strings, translate/update the few plural forms it contains as necessary and then generate the binary translation mudlet_en_US.qm file and merge it into the repo (see Translating Mudlet - English (American) translation).
    3. ☐ merge outstanding approved pull requests
    4. ☐ create a new release-<version> branch off development
    5. ☐ go through every single commit and ensure all new functionality is documented
    6. ☐ update http://www.mudlet.org/geyser/files/index.html (need to document how to upload)
    7. ☐ update built-in packages and scripts
    8. ☐ update edbee to latest
    9. ☐ go through every single commit and write up a newspost with the latest highlights
  2. on release day
    1. ☐ create a new release in dblsqd
    2. ☐ merge latest translations from Crowdin
    3. ☐ merge latest autocomplete json
    4. ☐ update mudlet.pro and CMakeLists.txt to new version and strip out BUILD to be empty in release branch (release process starts here)
    5. ☐ tag in git
    6. ☐ reset BUILD in release branch to be -dev
    7. ☐ test that all binaries launch and work
    8. ☐ close github milestone
    9. update downloads on mudlet.org
    10. ☐ post news on mudlet.org - for all languages
    11. ☐ Create Quick Redirect like mudlet.org/3-23
    12. ☐ post news to https://launchpad.net/mudlet
    13. ☐ make a proper github release (use turndown to convert release post html to markdown)
    14. ☐ post thread on forums.mudlet.org
    15. ☐ post update on achaea, starmourn, imperian, mudconnect.com, topmudsites.com forums, softpedia
    16. ☐ post update on twitter, mud.social, reddit, http://arkadia.rpg.pl, torilmud, muder.ru
    17. ☐ email to releaseradar@github.com about the update
    18. ☐ submit mudlet windows installer to avg and avast whitelisting
    19. ☐ merge, don't squash or rebase, the release branch into development (ensure -dev suffix is present)
    20. ☐ merge development into master branch
    21. ☐ update Linux distro maintainers, flag package outdated on arch (release process ends here)

Individual contributor TODOs