New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update MAINTAINERS.md #6299
Update MAINTAINERS.md #6299
Conversation
add post-release deployment instructions
Left a comment, but otherwise looks good - thanks! |
- [ ] 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` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thoughts @zalberico?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the read command won't work if the clocks on the servers get out of sync for some reason, but otherwise should be fine (I typically just ssh into all of them myself)
MAINTAINERS.md
Outdated
@@ -143,6 +146,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` | |||
|
|||
### Release Next Release Candidate | |||
|
|||
We'll now need to **IMMEDIATELY** deploy the new release candidate to the pre-release moons. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Might be worth explicitly saying before anything new merges into develop after branching for release (the why)?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Deploying directly from release branches to marnec via tooling will fix this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Left some minor comments, but looks good.
add post-release deployment instructions