Revision as of 20:43, 30 October 2018

Mudlet release checklist

☐ 5 days before the release
☐ update mudlet.ts with the latest translations strings for translators to translate
☐ merge outstanding approved pull requests
☐ create a new release-<version> branch off development
☐ go through every single commit 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
☐ update mudlet.pro and CMakeLists.txt to new version and strip out BUILD to be empty in development branch (release process starts here)
☐ tag in git
☐ reset BUILD in development branch to be -dev
☐ test that all binaries launch and work
☐ close github milestone
☐ post news on mudlet.org
☐ post news to https://launchpad.net/mudlet
☐ make a proper github release
☐ post thread on forums.mudlet.org
☐ post update on achaea, lusternia, imperian, dsl-mud.org, mudconnect.com, topmudsites.com forums, softpedia
☐ post update on twitter, mud.social, reddit, http://arkadia.rpg.pl, torilmud, muder.ru
☐ submit mudlet windows installer to avg and avast whitelisting
☐ merge release branch into <code<development
☐ merge development into master branch
☐ update Linux distro maintainers, flag package outdated on arch (release process ends here)

@@ Line 2: / Line 2: @@
 # ☐ 5 days before the release
 # ☐ update <code>mudlet.ts</code> with the latest translations strings for translators to translate
+# ☐ merge outstanding approved pull requests
 # ☐ create a new <code>release-<version></code> branch off <code>development</code>
 # ☐ go through every single commit and ensure all new functionality is documented