diff --git a/MAINTAINERS.md b/MAINTAINERS.md
index c58c227a9..8967439af 100644
--- a/MAINTAINERS.md
+++ b/MAINTAINERS.md
@@ -126,7 +126,8 @@ git push origin <tagname>
 - [ ] 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`
+- [ ] Install the contents of the `%kids` desk on `~marnec-dozzod-marzod` into our `%base`: `|merge %base ~marnec-dozzod-marzod %kids, =gem %
+`
 - [ ] 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.
@@ -143,6 +144,17 @@ git push origin <tagname>
 - [ ] Merge `master` back into `develop`.
 - [ ] Cut a new release branch from `develop`.  The branch should have the format `release/urbit-os-vX.XX`
 
+### Post-Release Deployments
+
+We'll now need to 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
+  - [ ] `|merge %kids our %base, =gem %only-that` to OTA the release candidate to subscribers
+- When ready to deploy the release candidate to App Developers, on `~doznec-dozzod-marzod`:
+  - [ ] `|merge %base ~marnec-dozzod-marzod %kids, =gem %only-that` to update `~doznec` with the release candidate
+  - [ ] `|merge %kids our %base, =gem %only-that` to OTA the release candidate to subscribers
+
 ### Post-Release Checks
 - [ ] Check that `~marzod` and other distribution stars are receiving the update by running `|ames-sift ~zod` and `|ames-verb %rcv %ges`.  You should see lots of packets from `~zod`.  Once you have confirmed packets are flowing, run `|ames-sift` and `|ames-verb` with no arguments to reset the verbosity state.
 - [ ] Check that planets are receiving the update.  They should start updating within an hour or so.