From e44a661076fd248f600a3696dada00f8ba31a5fe Mon Sep 17 00:00:00 2001 From: Josh Lehman Date: Tue, 7 Feb 2023 10:35:43 -0800 Subject: [PATCH] Update MAINTAINERS.md --- MAINTAINERS.md | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/MAINTAINERS.md b/MAINTAINERS.md index 9e04d4a29..bedd9f666 100644 --- a/MAINTAINERS.md +++ b/MAINTAINERS.md @@ -126,7 +126,10 @@ git push origin - [ ] ssh into `~zod` - [ ] Check to ensure that nobody else is ssh'd into `~zod`, by running `screen -ls` and verifying no sessions are attached. - [ ] Attach to the screen session using `screen -x` -- [ ] Install the contents of the `%kids` desk on `~marnec-dozzod-marzod` into our `%base`: `|merge %base ~marnec-dozzod-marzod %kids, =gem %only-that` +- [ ] Ensure that the release candidate was correctly propagated through the prerelease moons + - Use `-read %z ~SHIP %DESK da+now /` to check desk hashes + - [ ] Run the above check on the following [SHIP DESK] pairs: [~marnec-dozzod-marzod %base], [~marnec-dozzod-marzod %kids], [~doznec-dozzod-marzod %base], [~doznec-dozzod-marzod %kids] — **they should all match** +- [ ] Install the contents of the `%kids` desk on `~doznec-dozzod-marzod` into our `%base`: `|merge %base ~doznec-dozzod-marzod %kids, =gem %only-that` - [ ] Check that `~zod` has updated to the latest release. For a Kelvin release, you can run `zuse` in the Dojo. Each non-Kelvin release might its own way of checking whether the update has completed, possibly through checking the `%cz` hash of the `%base` desk matches the hash on `~marnec-dozzod-marzod` by comparing the outputs of `+vat %base` on both ships. - [ ] Merge `~zod`'s `%base` desk into its `%kids` desk to distribute the new code to the network: `|merge %kids our %base, =gem %only-that` - [ ] Before exiting the screen session on `~zod`, make sure the screen session is not left in copy mode for a long period of time, since that will disrupt `~zod`'s operation. @@ -145,7 +148,7 @@ git push origin ### Release Next Release Candidate -We'll now need to deploy the new release candidate to the pre-release moons. +We'll now need to **IMMEDIATELY** deploy the new release candidate to the pre-release moons. - On `~marnec-dozzod-marzod`: - [ ] `|merge %base ~binnec-dozzod-marzod %kids, =gem %only-that` to update `~marnec` with the contents of the GH release branch