docs: add release preflight checklist - #666
Merged
Merged
Conversation
Require a fresh-node full sync and a full `quantus exercise` run on --dev before tagging a chain release. These would have caught the last ship-blocker (a binary that could not sync).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds
docs/RELEASE_PREFLIGHT.md: the checks we run before tagging or publishing aquantus-node/ runtime release.Why
The last ship-blocker (a binary that could not sync a live chain) would have been caught by starting a new node with an empty DB. CI green is not enough.
Gates
quantus exercise --fail-faston a local--devnode (full suite)try-runtimeif the runtime/migrations changedLive governance upgrade after the release exists stays in
RUNTIME_UPDATE.md.Test plan