Release Checklist
Revision as of 09:45, 8 February 2019 by Keneanung (talk | contribs) (→Individual contributor TODOs: Change URL to TODO list)
Mudlet release checklist
- 5 days before the release
- ☐ update
mudlet.ts
with the latest translations strings for translators to translate (using Q 5.12.2+lupdate -recursive ./src/ -ts ./translations/mudlet.ts
) - ☐ merge outstanding approved pull requests
- ☐ create a new
release-<version>
branch offdevelopment
- ☐ 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
- ☐ update
- 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 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
- ☐ update downloads on mudlet.org
- ☐ post news on mudlet.org
- ☐ 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, 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, don't squash or rebase, the release branch into
development
(ensure-dev
suffix is present) - ☐ merge
development
intomaster
branch - ☐ update Linux distro maintainers, flag package outdated on arch (release process ends here)