Release Checklist - Revision history

Vadi at 09:20, 26 December 2024

2024-12-26T09:20:09Z

Vadi at 19:18, 15 December 2024

2024-12-15T19:18:04Z

Vadi: /* Mudlet release checklist */

2024-02-01T06:49:35Z

Mudlet release checklist

Kebap: Move release day step 13 after step 10

2024-01-31T20:57:46Z

Move release day step 13 after step 10

Vadi: Improve chronological ordering and mention which steps can be done concurrently or sequentially

2024-01-28T21:12:43Z

Improve chronological ordering and mention which steps can be done concurrently or sequentially

Vadi at 17:52, 8 January 2024

2024-01-08T17:52:40Z

Vadi at 13:09, 2 April 2023

2023-04-02T13:09:41Z

Vadi: /* Mudlet release checklist */ geyser docs now automated

2023-03-22T12:08:08Z

Mudlet release checklist: geyser docs now automated

Vadi at 12:23, 19 March 2023

2023-03-19T12:23:38Z

Vadi at 12:22, 19 March 2023

2023-03-19T12:22:09Z

@@ Line 32: / Line 32: @@
 ## ☐ wait for the builds to complete...
 ## ☐ test that all binaries launch and work
-## ☐ manually upload artifacts to https://www.mudlet.org/wp-content/files/?C=M;O=D through webmin. Linux and macOS ones will be available as artifacts on the Github job, while Windows is an artifact on the Appveyor job.
+## ☐ [automated] ensure all artifacts have been uploaded to https://www.mudlet.org/all. Linux and macOS ones will be available as artifacts on the Github job, while Windows is an artifact on the Appveyor job.
-## ☐ manually link uploaded artifacts to dblsqd (see [1])
+## ☐ [automated] link uploaded artifacts to dblsqd (see [1])
 ## ☐ update [https://github.com/Mudlet/Mudlet/blob/development/.github/repo-metadata.yml repo-metadata.yml] to the next release version
 ## ☐ close current github milestone

@@ Line 55: / Line 55: @@
 ## ☐ merge <code>development</code> into <code>master</code> branch
 ## ☐ merge, don't squash or rebase, the release branch into development (but don't delete right away, keep it around for a potential hotfix if needed. Delete after the next release is done). Do it right away so next day's PTB's versions is the new release.
-## ☐ [https://www.mudlet.org/2021/10/trial-pay-out-to-popular-prs/ create polls] for most popular changes
+## ☐ create a poll in Discord - yes/no/abstain - if people like the new update or no

@@ Line 46: / Line 46: @@
 ## ☐ post to #announcements in Discord. Publish the post, then add a follow-up @everyone tag as a separate post. This will notify folks in the Mudlet server without showing the @everyone tag in all other syncronised servers
 ## ☐ post news to https://launchpad.net/mudlet
 ## ☐ post thread on forums.mudlet.org
 ## ☐ post update on achaea, starmourn, imperian, lusternia, pkuxkx.net, [http://linux.softpedia.com/get/GAMES-ENTERTAINMENT/MUD/Mudlet-45973.shtml softpedia]

@@ Line 31: / Line 31: @@
 ## ☐ reset BUILD in release branch to be -dev
 ## ☐ wait for the builds to complete...
 ## ☐ manually upload artifacts to https://www.mudlet.org/wp-content/files/?C=M;O=D through webmin. Linux and macOS ones will be available as artifacts on the Github job, while Windows is an artifact on the Appveyor job.
-## ☐ manually link uploaded artifacts to dblsqd[1]:
+## ☐ manually link uploaded artifacts to dblsqd (see [1])
 ## ☐ update [https://github.com/Mudlet/Mudlet/blob/development/.github/repo-metadata.yml repo-metadata.yml] to the next release version
 ## ☐ close current github milestone

@@ Line 1: / Line 1: @@
 = Mudlet release checklist =
 # 5 days before the release (14 if it's a long one)
 ## ☐ [automated] update <code>mudlet.ts</code> with the latest translations strings for translators to translate
 ## ☐ [automated] update <code>mudlet_en_US.ts</code> with the latest translation strings, translate/update the few plural forms it contains as necessary and then generate the binary translation <code>mudlet_en_US.qm</code> file and merge it into the repo (see [https://wiki.mudlet.org/w/Translating_Mudlet#English_.28American.29_translation Translating Mudlet - English (American) translation]).
 ## ☐ [automated] update [http://www.mudlet.org/geyser/files/index.html Geyser docs]
 ## ☐ [automated] update built-in packages and scripts (IRE mapping script, ...)
 ## ☐ [automated] update edbee to latest in our fork, and the subsequent submodule
 ## ☐ update Patreon supporters in About tab
 ## ☐ check all [https://github.com/Mudlet/Mudlet/issues?q=is%3Aissue+is%3Aopen+label%3Aregression regressions] to see if any must be fixed before the release
 ## ☐ get testers to sign off (via Discord reaction) that they tested the release and it is fine with them
 ### if a tester doesn't sign off for 2 releases, notify them, if they don't do it on the next one, remove them from the testers team
 # on release day
 ## ☐ merge latest translations from Crowdin
 ## ☐ merge all Area 51 functions into main wiki
 ## ☐ [https://wiki.mudlet.org/w/Manual:Lua_Functions?action=purge purge] Lua_Functions cache to ensure the latest functions are visible
 ## ☐ merge [[Update_lua_function_list|latest autocomplete json]]
 ## ☐ update mudlet.pro and CMakeLists.txt to new version and strip out BUILD to be empty in release branch (release process starts here)
-## ☐ tag in git
+## ☐ tag release in git and push
 ## ☐ manually create source code package [https://github.com/Mudlet/Mudlet/blob/33ad832253d6b6411d7c1132e68455742157d60d/CI/travis.linux.after_success.sh#L144 following this]
 ## ☐ reset BUILD in release branch to be -dev
@@ Line 29: / Line 34: @@
 ## ☐ manually link uploaded artifacts to dblsqd[1]:
 ## ☐ test that all binaries launch and work
 ## ☐ update [https://github.com/Mudlet/Mudlet/blob/development/.github/repo-metadata.yml repo-metadata.yml] to the next release version
 ## ☐ close current github milestone
 ## ☐ [[Howto:Update Downloads|update downloads on mudlet.org]]
 ## ☐ [automated] create changelog with [https://github.com/Mudlet/Mudlet/actions/workflows/generate-changelog.yml a github action]
-## ☐ create a proper github release
+## ☐ create a proper github release using the draft created earlier
-## ☐ [automated] insert list of translators into the post ([https://www.mudlet.org/thank-translators/crowdin.php tool])
+## ☐ [automated] insert list of translators into the release post ([https://www.mudlet.org/thank-translators/crowdin.php tool])
-## ☐ [automated] insert list of coders into the post ([https://github.com/Mudlet/Mudlet/actions/workflows/generate-coder-attribution.yml tool])
+## ☐ [automated] insert list of coders into the release post ([https://github.com/Mudlet/Mudlet/actions/workflows/generate-coder-attribution.yml tool])
-## ☐ publish release post, it will be automatically posted to mudlet.org on save
+## ☐ publish release post and it will be automatically posted to mudlet.org on save
 ## ☐ delay rest of announcements until 3-4 days past the release; post when there are no verified issues in update
-## ☐ post to #announcements in Discord. Publish the post, then add a follow-up @everyone tag. This will notify folks in the Mudlet server without showing the @everyone tag in all other syncronised servers
+### everything above the step must be done sequentially, while everything below this step can be done concurrently.
 ## ☐ post news to https://launchpad.net/mudlet
 ## ☐ post thread on forums.mudlet.org
@@ Line 46: / Line 51: @@
 ## ☐ email to releaseradar@github.com about the update
 ## ☐ submit mudlet windows installer to avg and avast whitelisting
 ## ☐ merge <code>development</code> into <code>master</code> branch
 ## ☐ merge, don't squash or rebase, the release branch into development (but don't delete right away, keep it around for a potential hotfix if needed. Delete after the next release is done). Do it right away so next day's PTB's versions is the new release.
 ## ☐ [https://www.mudlet.org/2021/10/trial-pay-out-to-popular-prs/ create polls] for most popular changes

@@ Line 7: / Line 7: @@
 ## ☐ create a new <code>release-<version></code> branch off <code>development</code>
 ## ☐ go through every single commit (in main repo and installers) and ensure all new functionality is documented
-## ☐ update http://www.mudlet.org/geyser/files/index.html (need to document how to upload)
+## ☐ [automated] update [http://www.mudlet.org/geyser/files/index.html Geyser docs]
 ## ☐ [automated] update built-in packages and scripts (IRE mapping script, ...)
 ## ☐ [automated] update edbee to latest in our fork, and the subsequent submodule

← Older revision		Revision as of 12:23, 19 March 2023
Line 46:		Line 46:
	## ☐ merge, don't squash or rebase, the release branch into development (but don't delete right away, keep it around for a potential hotfix if needed. Delete after the next release is done). Do it right away so next day's PTB's versions is the new release.		## ☐ merge, don't squash or rebase, the release branch into development (but don't delete right away, keep it around for a potential hotfix if needed. Delete after the next release is done). Do it right away so next day's PTB's versions is the new release.
	## ☐ [https://www.mudlet.org/2021/10/trial-pay-out-to-popular-prs/ create polls] for most popular changes		## ☐ [https://www.mudlet.org/2021/10/trial-pay-out-to-popular-prs/ create polls] for most popular changes
−	~~## ☐ update [https://github.com/Mudlet/Mudlet/blob/development/.github/repo-metadata.yml repo-metadata.yml]~~

← Older revision		Revision as of 12:22, 19 March 2023
Line 46:		Line 46:
	## ☐ merge, don't squash or rebase, the release branch into development (but don't delete right away, keep it around for a potential hotfix if needed. Delete after the next release is done). Do it right away so next day's PTB's versions is the new release.		## ☐ merge, don't squash or rebase, the release branch into development (but don't delete right away, keep it around for a potential hotfix if needed. Delete after the next release is done). Do it right away so next day's PTB's versions is the new release.
	## ☐ [https://www.mudlet.org/2021/10/trial-pay-out-to-popular-prs/ create polls] for most popular changes		## ☐ [https://www.mudlet.org/2021/10/trial-pay-out-to-popular-prs/ create polls] for most popular changes
		+	## ☐ update [https://github.com/Mudlet/Mudlet/blob/development/.github/repo-metadata.yml repo-metadata.yml]