Difference between revisions of "Release Checklist"

From Mudlet
Jump to navigation Jump to search
(11 intermediate revisions by 4 users 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 -recursive ./src/ -ts ./translations/mudlet.ts</code>)
+
## ☐ 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</code>), NB the <code>-recursive</code> option is not needed as it is the default option.
 +
## ☐ 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
 
## ☐ create a new <code>release-<version></code> branch off <code>development</code>
 
## ☐ create a new <code>release-<version></code> branch off <code>development</code>
Line 12: Line 13:
 
## ☐ create a new release in dblsqd
 
## ☐ create a new release in dblsqd
 
## ☐ merge latest translations from Crowdin
 
## ☐ merge latest translations from Crowdin
−
## ☐ merge latest autocomplete json
+
## ☐ merge [[Update_lua_function_list|latest autocomplete json]]
−
## ☐ update mudlet.pro and CMakeLists.txt to new version and strip out BUILD to be empty in development branch (release process starts here)
+
## ☐ update mudlet.pro and CMakeLists.txt to new version and strip out BUILD to be empty in release branch (release process starts here)
 
## ☐ tag in git
 
## ☐ tag in git
−
## ☐ reset BUILD in development branch to be -dev
+
## ☐ reset BUILD in release branch to be -dev
 
## ☐ test that all binaries launch and work
 
## ☐ test that all binaries launch and work
 
## ☐ close github milestone
 
## ☐ close github milestone
 +
## ☐ [[Howto:Update Downloads|update downloads on mudlet.org]]
 
## ☐ post news on mudlet.org
 
## ☐ post news on mudlet.org
 +
## ☐ Create Quick Redirect like mudlet.org/3-23
 
## ☐ post news to https://launchpad.net/mudlet
 
## ☐ post news to https://launchpad.net/mudlet
−
## ☐ make a proper github release
+
## ☐ make a proper github release (use [http://domchristie.github.io/turndown/ turndown] to convert release post html to markdown)
 
## ☐ post thread on forums.mudlet.org
 
## ☐ post thread on forums.mudlet.org
−
## ☐ post update on achaea, lusternia, imperian, dsl-mud.org, mudconnect.com, topmudsites.com forums, [http://linux.softpedia.com/get/GAMES-ENTERTAINMENT/MUD/Mudlet-45973.shtml softpedia]
+
## ☐ post update on achaea, starmourn, imperian, mudconnect.com, topmudsites.com forums, [http://linux.softpedia.com/get/GAMES-ENTERTAINMENT/MUD/Mudlet-45973.shtml softpedia]
 
## ☐ post update on twitter, mud.social, reddit, http://arkadia.rpg.pl, torilmud, muder.ru
 
## ☐ post update on twitter, mud.social, reddit, http://arkadia.rpg.pl, torilmud, muder.ru
 
## ☐ submit mudlet windows installer to avg and avast whitelisting
 
## ☐ submit mudlet windows installer to avg and avast whitelisting
−
## ☐ merge release branch into <code>development</code> (ensure <code>-dev</code> suffix is present)
+
## ☐ merge, don't squash or rebase, the release branch into <code>development</code> (ensure <code>-dev</code> suffix is present)
 
## ☐ merge <code>development</code> into <code>master</code> branch
 
## ☐ merge <code>development</code> into <code>master</code> branch
 
## ☐ update Linux distro maintainers, flag package outdated on arch (release process ends here)
 
## ☐ update Linux distro maintainers, flag package outdated on arch (release process ends here)
  
 
= Individual contributor TODOs =
 
= Individual contributor TODOs =
−
* keneanung: https://gist.github.com/keneanung/0d8def8454c912f28842d3749ad65f00
+
* keneanung: https://github.com/users/keneanung/projects/1
 
* vadi: https://gist.github.com/vadi2/1fb249c48dead71b9641f840622e8495
 
* vadi: https://gist.github.com/vadi2/1fb249c48dead71b9641f840622e8495
 +
 +
[[Category: Mudlet Admin Manual]]

Revision as of 08:38, 7 April 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
    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. ☐ submit mudlet windows installer to avg and avast whitelisting
    18. ☐ merge, don't squash or rebase, the release branch into development (ensure -dev suffix is present)
    19. ☐ merge development into master branch
    20. ☐ update Linux distro maintainers, flag package outdated on arch (release process ends here)

Individual contributor TODOs

Retrieved from "https://wiki.mudlet.org/index.php?title=Release_Checklist&oldid=5504"