Difference between revisions of "Release Checklist"
Jump to navigation
Jump to search
(29 intermediate revisions by 4 users not shown) | |||
Line 1: | Line 1: | ||
= Mudlet release checklist = | = Mudlet release checklist = | ||
− | # | + | # 5 days before the release |
− | # ☐ update <code>mudlet.ts</code> with the latest translations strings for translators to translate | + | ## ☐ announce start of testing in Discord channel #mudlet-testing (add template text here), and link to latest download builds (from [https://make.mudlet.org/snapshots Latest Branch Snapshots], but double check that sha matches [https://github.com/Mudlet/Mudlet/commits/development the latest commit]) |
− | # ☐ merge outstanding approved pull requests | + | ## ☐ 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>) |
− | # ☐ create a new <code>release-<version></code> branch off <code>development</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]). |
− | # ☐ go through every single commit and ensure all new functionality is documented | + | ## ☐ merge outstanding approved pull requests |
− | # ☐ update http://www.mudlet.org/geyser/files/index.html (need to document how to upload) | + | ## ☐ create a new <code>release-<version></code> branch off <code>development</code> |
− | # ☐ update built-in packages and scripts | + | ## ☐ go through every single commit (in main repo and isntallers) and ensure all new functionality is documented |
− | # ☐ update edbee to latest | + | ## ☐ update http://www.mudlet.org/geyser/files/index.html (need to document how to upload) |
− | # ☐ go through every single commit and write up a newspost with the latest highlights | + | ## ☐ update built-in packages and scripts |
− | # | + | ## ☐ update edbee to latest |
− | # ☐ create a new release in dblsqd | + | ## ☐ go through every single commit and write up a newspost with the latest highlights |
− | # ☐ merge latest translations from Crowdin | + | # on release day |
− | # ☐ update mudlet.pro and CMakeLists.txt to new version and strip out BUILD to be empty in | + | ## ☐ create a new release in dblsqd |
− | # ☐ tag in git | + | ## ☐ merge latest translations from Crowdin |
− | # ☐ reset BUILD in | + | ## ☐ merge [[Update_lua_function_list|latest autocomplete json]] |
− | # ☐ test that all binaries launch and work | + | ## ☐ update mudlet.pro and CMakeLists.txt to new version and strip out BUILD to be empty in release branch (release process starts here) |
− | # ☐ close github milestone | + | ## ☐ tag in git |
− | # ☐ post news on mudlet.org | + | ## ☐ reset BUILD in release branch to be -dev |
− | # ☐ post news to https://launchpad.net/mudlet | + | ## ☐ test that all binaries launch and work |
− | # ☐ make a proper github release | + | ## ☐ close github milestone |
− | # ☐ post thread on forums.mudlet.org | + | ## ☐ [[Howto:Update Downloads|update downloads on mudlet.org]] |
− | # ☐ post update on achaea, | + | ## ☐ post news on mudlet.org - [https://github.com/Mudlet/Mudlet/issues/2550 for all languages]: |
− | # ☐ post update on twitter, mud.social, reddit, http://arkadia.rpg.pl, torilmud, muder.ru | + | ### Select English news and "Duplicate this". Repeat these steps for every target language. |
− | # ☐ submit mudlet windows installer to avg and avast whitelisting | + | ### In right-hand side "Languages" tab, change language from English to German. Page will reload. Then write name of English post in the English box. Suggestions will appear. Click the original post to confirm. Translations are now linked. In the end, all languages should be interlinked. |
− | # | + | ## ☐ Create Quick Redirect like mudlet.org/3-23 |
− | # ☐ merge <code>development</code> into <code>master</code> branch | + | ## ☐ post news to https://launchpad.net/mudlet |
− | # ☐ update Linux distro maintainers, flag package outdated on arch (release process ends here) | + | ## ☐ 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 update on achaea, starmourn, imperian, 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 | ||
+ | ## ☐ email to releaseradar@github.com about the update | ||
+ | ## ☐ submit mudlet windows installer to avg and avast whitelisting | ||
+ | ## ☐ merge <code>development</code> into <code>master</code> branch | ||
+ | ## ☐ update Linux distro maintainers, flag package outdated on arch (release process ends here) | ||
+ | ## ☐ merge, don't squash or rebase, the release branch into development (but don't delete, keep it around for a potential hotfix if needed) | ||
= Individual contributor TODOs = | = Individual contributor TODOs = | ||
− | https:// | + | * keneanung: https://github.com/users/keneanung/projects/1 |
− | + | ||
+ | [[Category: Mudlet Admin Manual]] |
Revision as of 11:32, 11 November 2019
Mudlet release checklist
- 5 days before the release
- ☐ announce start of testing in Discord channel #mudlet-testing (add template text here), and link to latest download builds (from Latest Branch Snapshots, but double check that sha matches the latest commit)
- ☐ 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
) - ☐ 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 translationmudlet_en_US.qm
file and merge it into the repo (see Translating Mudlet - English (American) translation). - ☐ merge outstanding approved pull requests
- ☐ create a new
release-<version>
branch offdevelopment
- ☐ go through every single commit (in main repo and isntallers) and ensure all new functionality is documented
- ☐ update http://www.mudlet.org/geyser/files/index.html (need to document how to upload)
- ☐ update built-in packages and scripts
- ☐ update edbee to latest
- ☐ go through every single commit and write up a newspost with the latest highlights
- on release day
- ☐ create a new release in dblsqd
- ☐ merge latest translations from Crowdin
- ☐ merge latest autocomplete json
- ☐ 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
- ☐ reset BUILD in release branch to be -dev
- ☐ test that all binaries launch and work
- ☐ close github milestone
- ☐ update downloads on mudlet.org
- ☐ post news on mudlet.org - for all languages:
- Select English news and "Duplicate this". Repeat these steps for every target language.
- In right-hand side "Languages" tab, change language from English to German. Page will reload. Then write name of English post in the English box. Suggestions will appear. Click the original post to confirm. Translations are now linked. In the end, all languages should be interlinked.
- ☐ Create Quick Redirect like mudlet.org/3-23
- ☐ post news to https://launchpad.net/mudlet
- ☐ make a proper github release (use turndown to convert release post html to markdown)
- ☐ post thread on forums.mudlet.org
- ☐ post update on achaea, starmourn, imperian, topmudsites.com forums, softpedia
- ☐ 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
development
intomaster
branch - ☐ update Linux distro maintainers, flag package outdated on arch (release process ends here)
- ☐ merge, don't squash or rebase, the release branch into development (but don't delete, keep it around for a potential hotfix if needed)