Release Checklist

Mudlet release checklist

1. ☐ 5 days before the release
2. ☐ update mudlet.ts with the latest translations strings for translators to translate
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
10. ☐ on release day
11. ☐ create a new release in dblsqd
12. ☐ merge latest translations from Crowdin
13. ☐ merge latest autocomplete json
14. ☐ update mudlet.pro and CMakeLists.txt to new version and strip out BUILD to be empty in development branch (release process starts here)
15. ☐ tag in git
16. ☐ reset BUILD in development branch to be -dev
17. ☐ test that all binaries launch and work
18. ☐ close github milestone
19. ☐ post news on mudlet.org
20. ☐ post news to https://launchpad.net/mudlet
21. ☐ make a proper github release
22. ☐ post thread on forums.mudlet.org
23. ☐ post update on achaea, lusternia, imperian, dsl-mud.org, mudconnect.com, topmudsites.com forums, softpedia
24. ☐ post update on twitter, mud.social, reddit, http://arkadia.rpg.pl, torilmud, muder.ru
25. ☐ submit mudlet windows installer to avg and avast whitelisting
26. ☐ merge release branch into development (ensure -dev suffix is present)
27. ☐ merge development into master branch
28. ☐ update Linux distro maintainers, flag package outdated on arch (release process ends here)

Individual contributor TODOs

https://gist.github.com/keneanung/0d8def8454c912f28842d3749ad65f00 https://gist.github.com/vadi2/1fb249c48dead71b9641f840622e8495