Release Checklist

From Mudlet
Revision as of 13:48, 12 November 2018 by Kebap (talk | contribs) (Adjust layout for improved readability)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Mudlet release checklist

  1. 5 days before the release
    1. ☐ update mudlet.ts with the latest translations strings for translators to translate
    2. ☐ merge outstanding approved pull requests
    3. ☐ create a new release-<version> branch off development
    4. ☐ go through every single commit and ensure all new functionality is documented
    5. ☐ update http://www.mudlet.org/geyser/files/index.html (need to document how to upload)
    6. ☐ update built-in packages and scripts
    7. ☐ update edbee to latest
    8. ☐ 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 development branch (release process starts here)
    5. ☐ tag in git
    6. ☐ reset BUILD in development branch to be -dev
    7. ☐ test that all binaries launch and work
    8. ☐ close github milestone
    9. ☐ post news on mudlet.org
    10. ☐ post news to https://launchpad.net/mudlet
    11. ☐ make a proper github release
    12. ☐ post thread on forums.mudlet.org
    13. ☐ post update on achaea, lusternia, imperian, dsl-mud.org, mudconnect.com, topmudsites.com forums, softpedia
    14. ☐ post update on twitter, mud.social, reddit, http://arkadia.rpg.pl, torilmud, muder.ru
    15. ☐ submit mudlet windows installer to avg and avast whitelisting
    16. ☐ merge release branch into development (ensure -dev suffix is present)
    17. ☐ merge development into master branch
    18. ☐ update Linux distro maintainers, flag package outdated on arch (release process ends here)

Individual contributor TODOs