Difference between revisions of "Release Checklist"
Jump to navigation
Jump to search
| 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 | ||
| + | # ☐ create a new <code>release-<version></code> branch off <code>development</code> | ||
# ☐ go through every single commit and ensure all new functionality is documented | # ☐ 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 http://www.mudlet.org/geyser/files/index.html (need to document how to upload) | ||
| Line 6: | Line 8: | ||
# ☐ update edbee to latest | # ☐ update edbee to latest | ||
# ☐ go through every single commit and write up a newspost with the latest highlights | # ☐ go through every single commit and write up a newspost with the latest highlights | ||
| − | # ☐ update mudlet.pro and CMakeLists.txt to new version and strip out BUILD to be empty in development branch | + | # ☐ on release day |
| − | + | # ☐ create a new release in dblsqd | |
| − | # ☐ | + | # ☐ 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 | # ☐ reset BUILD in development branch to be -dev | ||
# ☐ test that all binaries launch and work | # ☐ test that all binaries launch and work | ||
| − | |||
# ☐ close github milestone | # ☐ close github milestone | ||
# ☐ post news on mudlet.org | # ☐ post news on mudlet.org | ||
| Line 23: | Line 22: | ||
# ☐ post update on twitter, mud.social, reddit, http://arkadia.rpg.pl, torilmud, muder.ru | # ☐ post update on twitter, mud.social, reddit, http://arkadia.rpg.pl, torilmud, muder.ru | ||
# ☐ submit mudlet windows installer to avg and avast whitelisting | # ☐ submit mudlet windows installer to avg and avast whitelisting | ||
| − | # ☐ | + | # ☐ merge release branch into <code<development</code> |
| + | # ☐ merge <code>development</code> into <code>master</code> branch | ||
# ☐ update Linux distro maintainers, flag package outdated on arch (release process ends here) | # ☐ update Linux distro maintainers, flag package outdated on arch (release process ends here) | ||
Revision as of 08:48, 25 October 2018
Mudlet release checklist
- ☐ 5 days before the release
- ☐ update
mudlet.tswith the latest translations strings - ☐ 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
- ☐ on release day
- ☐ create a new release in dblsqd
- ☐ 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
developmentintomasterbranch - ☐ 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