Difference between revisions of "Release Checklist"

From Mudlet
Jump to navigation Jump to search
(Adjust layout for improved readability)
(12 intermediate revisions by one other user not shown)
Line 1: Line 1:
 
= Mudlet release checklist =
 
= Mudlet release checklist =
−
# ☐ ensure windows, mac, linux generic installers and the ubuntu ppa are good to go
+
# 5 days before the release
−
# ☐ go through every single commit and ensure all new functionality is documented
+
## ☐ update <code>mudlet.ts</code> with the latest translations strings for translators to translate
−
# ☐ update http://www.mudlet.org/geyser/files/index.html (need to document how to upload)
+
## ☐ merge outstanding approved pull requests
−
# ☐ update built-in packages and scripts
+
## ☐ create a new <code>release-<version></code> branch off <code>development</code>
−
# ☐ update edbee to latest
+
## ☐ go through every single commit and ensure all new functionality is documented
−
# ☐ go through every single commit and write up a newspost with the latest highlights
+
## ☐ update http://www.mudlet.org/geyser/files/index.html (need to document how to upload)
−
# ☐ update src.pro and CMakeLists.txt to new version and strip out BUILD to be empty in development branch
+
## ☐ update built-in packages and scripts
−
# ☐ tag in git (release process starts here)
+
## ☐ update edbee to latest
−
# ☐ merge latest development to master branch
+
## ☐ go through every single commit and write up a newspost with the latest highlights
−
# ☐ make windows installer
+
# on release day
−
# ☐ make linux installers
+
## ☐ create a new release in dblsqd
−
# ☐ update Ubuntu PPA
+
## ☐ merge latest translations from Crowdin
−
# ☐ reset BUILD in development branch to be -dev
+
## ☐ merge latest autocomplete json
−
# ☐ test that all binaries launch and work
+
## ☐ update mudlet.pro and CMakeLists.txt to new version and strip out BUILD to be empty in development branch (release process starts here)
−
# ☐ close github milestone
+
## ☐ tag in git
−
# ☐ post news on mudlet.org
+
## ☐ reset BUILD in development branch to be -dev
−
# ☐ post news to https://launchpad.net/mudlet
+
## ☐ test that all binaries launch and work
−
# ☐ make a proper github release
+
## ☐ close github milestone
−
# ☐ post thread on forums.mudlet.org
+
## ☐ post news on mudlet.org
−
# ☐ post update on achaea, lusternia, imperian, dsl-mud.org, mudconnect.com, topmudsites.com forums, [http://linux.softpedia.com/get/GAMES-ENTERTAINMENT/MUD/Mudlet-45973.shtml softpedia]
+
## ☐ post news to https://launchpad.net/mudlet
−
# ☐ post update on twitter, reddit, http://arkadia.rpg.pl, torilmud
+
## ☐ make a proper github release
−
# ☐ update Linux distro maintainers, flag package outdated on arch (release process ends here)
+
## ☐ post thread on forums.mudlet.org
−
 
+
## ☐ post update on achaea, lusternia, imperian, dsl-mud.org, mudconnect.com, topmudsites.com forums, [http://linux.softpedia.com/get/GAMES-ENTERTAINMENT/MUD/Mudlet-45973.shtml softpedia]
−
= Post 3.0 checklist =
+
## ☐ post update on twitter, mud.social, reddit, http://arkadia.rpg.pl, torilmud, muder.ru
−
# ☑ merge release_30 into development and remove the branch (see https://github.com/Mudlet/Mudlet/pull/367 for some period discussion): http://wiki.mudlet.org/w/The_Merge
+
## ☐ submit mudlet windows installer to avg and avast whitelisting
−
# ☑ migrate the project from launchpad.net to github.com (help wanted)
+
## ☐ merge release branch into <code>development</code> (ensure <code>-dev</code> suffix is present)
−
# ☑ merge release_31 into development and remove the branch: http://wiki.mudlet.org/w/The_Merge
+
## ☐ merge <code>development</code> into <code>master</code> branch
−
# ☑ move vadi2/mudlet-lua into main tree (https://github.com/Mudlet/Mudlet/pull/832)
+
## ☐ update Linux distro maintainers, flag package outdated on arch (release process ends here)
−
# apply clang-format to all files
 
−
# enforce clang-format on commit & pr acceptance
 
−
# upgrade mudlet.org linode image (help wanted)
 
−
# in general, 4.0 is about i18n support - but as always, feel free to work on whatever interests you
 
−
# (From SlySven): unify exit "directions" into single QPair<quint8,QString> item {Existing DirCodeNumber + 13 for special exits, QString() for normal/QString("special exit name") for special exits} - makes it possible to streamline TRoom class and helps for I18n as we can drop NLS {Native Language Support} strings in for directions 1-12 if needed...!
 
−
# (From SlySven): Revamp 2D mapper:   
 
−
#* use "stub" out to 0.5x inter-room distance for all actual orthogonal/diagonal exits and draw exit lines from end of there to corresponding opposite exit in destination room (if present)/reverse exit in destination room (otherwise)/center of exit room (fallback).  Choosing to call this "Z" exits to reflect east exit from one room going to west exit in second room where the first room is north of the second.
 
−
#* add drawing support for doors on stub exits/custom lines
 
−
#* add stub special exits (for those odd exits which you do no yet know where they go) together with room indications for (at least) one of such things being present and also indication of a special exit without a custom exit line representation (again to show presence of such a thing).
 
−
# (From SlySven): Revamp 3D mapper:
 
−
#* port away from deprecated QGLWidget usage (it'll cause us less [https://bugreports.qt.io/browse/QTBUG-39210?focusedCommentId=267859&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-267859 issues on mac] too)
 
−
#* rewrite code to use modern (indirect) OpenGL 3.0+ - would be needed to port to OpenGLES (e.g. Raspberry Pi) platforms anyway.
 
−
#* generally clean up the 3D paintGL() code - it is rather messy at present with redundant/ineffective calls.
 
  
 
= Individual contributor TODOs =
 
= Individual contributor TODOs =
−
https://gist.github.com/keneanung/0d8def8454c912f28842d3749ad65f00
+
* keneanung: https://gist.github.com/keneanung/0d8def8454c912f28842d3749ad65f00
−
https://gist.github.com/vadi2/1fb249c48dead71b9641f840622e8495
+
* vadi: https://gist.github.com/vadi2/1fb249c48dead71b9641f840622e8495

Revision as of 13:48, 12 November 2018

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

Retrieved from "https://wiki.mudlet.org/index.php?title=Release_Checklist&oldid=5315"