chore(.github): Add release verification prompts to PR template section "Upgrade Considerations" #10444
+1
−1
Conversation
This file contains 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
Deploying agoric-sdk with
|
| Latest commit: |
efce9a3
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://3f3bfb0c.agoric-sdk.pages.dev |
| Branch Preview URL: | https://gibson-2024-11-release-verif.agoric-sdk.pages.dev |
gibson042
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
A topic in last week's kernel meeting was the burden of verifying releases, and even of determining what to verify and how to do so. This is an attempt to make that explicit at a much earlier point in development, with hints regarding future automation potential but no firm commitment of such. Assuming this lands, I expect release instructions to include collecting steps from all constituent PRs and post-release cleanup of any relevant scripts.
Security Considerations
n/a
Scaling Considerations
n/a
Documentation Considerations
n/a
Testing Considerations
n/a
Upgrade Considerations
This is intended to increase the maturity of our upgrade process.