Difference between revisions of "Release Checklist"

From Mudlet
Jump to navigation Jump to search
m
(21 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
+
## ☐ 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>)
# ☐ merge outstanding approved pull requests
+
## ☐ 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]).
# ☐ create a new <code>release-<version></code> branch off <code>development</code>
+
## ☐ merge outstanding approved pull requests
# ☐ go through every single commit and ensure all new functionality is documented
+
## ☐ create a new <code>release-<version></code> branch off <code>development</code>
# ☐ update http://www.mudlet.org/geyser/files/index.html (need to document how to upload)
+
## ☐ go through every single commit and ensure all new functionality is documented
# ☐ update built-in packages and scripts
+
## ☐ update http://www.mudlet.org/geyser/files/index.html (need to document how to upload)
# ☐ update edbee to latest
+
## ☐ update built-in packages and scripts
# ☐ go through every single commit and write up a newspost with the latest highlights
+
## ☐ update edbee to latest
# on release day
+
## ☐ go through every single commit and write up a newspost with the latest highlights
# ☐ create a new release in dblsqd
+
# on release day
# ☐ merge latest translations from Crowdin
+
## ☐ create a new release in dblsqd
# ☐ update mudlet.pro and CMakeLists.txt to new version and strip out BUILD to be empty in development branch (release process starts here)
+
## ☐ merge latest translations from Crowdin
# ☐ tag in git
+
## ☐ merge [[Update_lua_function_list|latest autocomplete json]]
# ☐ reset BUILD in development branch to be -dev
+
## ☐ update mudlet.pro and CMakeLists.txt to new version and strip out BUILD to be empty in release branch (release process starts here)
# ☐ test that all binaries launch and work
+
## ☐ tag in git
# ☐ close github milestone
+
## ☐ reset BUILD in release branch to be -dev
# ☐ post news on mudlet.org
+
## ☐ test that all binaries launch and work
# ☐ post news to https://launchpad.net/mudlet
+
## ☐ close github milestone
# ☐ make a proper github release
+
## ☐ [[Howto:Update Downloads|update downloads on mudlet.org]]
# ☐ post thread on forums.mudlet.org
+
## ☐ post news on mudlet.org - [https://github.com/Mudlet/Mudlet/issues/2550 for all languages]
# ☐ 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]
+
## ☐ Create Quick Redirect like mudlet.org/3-23
# ☐ post update on twitter, mud.social, reddit, http://arkadia.rpg.pl, torilmud, muder.ru
+
## ☐ post news to https://launchpad.net/mudlet
# ☐ submit mudlet windows installer to avg and avast whitelisting
+
## ☐ make a proper github release (use [http://domchristie.github.io/turndown/ turndown] to convert release post html to markdown)
# ☐ merge release branch into <code>development</code>
+
## ☐ post thread on forums.mudlet.org
# ☐ merge <code>development</code> into <code>master</code> branch
+
## ☐ post update on achaea, starmourn, imperian, mudconnect.com, topmudsites.com forums, [http://linux.softpedia.com/get/GAMES-ENTERTAINMENT/MUD/Mudlet-45973.shtml softpedia]
# ☐ update Linux distro maintainers, flag package outdated on arch (release process ends here)
+
## ☐ post update on twitter, mud.social, reddit, http://arkadia.rpg.pl, torilmud, muder.ru
 +
## ☐ email to releaseradar@github.com about the update
 +
## ☐ submit mudlet windows installer to avg and avast whitelisting
 +
## ☐ 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
 +
## ☐ update Linux distro maintainers, flag package outdated on arch (release process ends here)
  
 
= Individual contributor TODOs =
 
= Individual contributor TODOs =
https://gist.github.com/keneanung/0d8def8454c912f28842d3749ad65f00
+
* keneanung: https://github.com/users/keneanung/projects/1
https://gist.github.com/vadi2/1fb249c48dead71b9641f840622e8495
+
* vadi: https://gist.github.com/vadi2/1fb249c48dead71b9641f840622e8495
 +
 
 +
[[Category: Mudlet Admin Manual]]

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