Difference between revisions of "Release Checklist"

From Mudlet
Jump to navigation Jump to search
(Don't store line numbers in translations, too much churn)
 
(One intermediate revision by the same user not shown)
Line 1: Line 1:
 
= Mudlet release checklist =
 
= Mudlet release checklist =
 
# 5 days before the release
 
# 5 days before the release
## ☐ update <code>mudlet.ts</code> with the latest translations strings for translators to translate (using Q 5.12.2+ <code>lupdate ./src/ -ts ./translations/mudlet.ts -locations none</code>)
+
## ☐ update <code>mudlet.ts</code> with the latest translations strings for translators to translate (using Qt 5.12.2+ <code>lupdate -verbose -recursive ./src ./3rdparty/dblsqd/dblsqd ./3rdparty/edbee-lib/edbee-lib -ts ./translations/mudlet.ts</code>)
 
## ☐ update <code>mudlet_en_US.ts</code> with the latest translation strings, translate/update the few plural forms it contains as necessary and then generate the binary translation <code>mudlet_en_US.qm</code> file and merge it into the repo (see [https://wiki.mudlet.org/w/Translating_Mudlet#English_.28American.29_translation Translating Mudlet - English (American) translation]).
 
## ☐ update <code>mudlet_en_US.ts</code> with the latest translation strings, translate/update the few plural forms it contains as necessary and then generate the binary translation <code>mudlet_en_US.qm</code> file and merge it into the repo (see [https://wiki.mudlet.org/w/Translating_Mudlet#English_.28American.29_translation Translating Mudlet - English (American) translation]).
 
## ☐ merge outstanding approved pull requests
 
## ☐ merge outstanding approved pull requests

Latest revision as of 04:28, 10 July 2019

Mudlet release checklist

  1. 5 days before the release
    1. ☐ update mudlet.ts with the latest translations strings for translators to translate (using Qt 5.12.2+ lupdate -verbose -recursive ./src ./3rdparty/dblsqd/dblsqd ./3rdparty/edbee-lib/edbee-lib -ts ./translations/mudlet.ts)
    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