agoric-upgrade-13 #8588
Merged
agoric-upgrade-13 #8588
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
The commits are slightly different. The plan is to have master and the release branch diverge here. However I'll wait to update the base branch first. |
I presumed you would not want the documentation to diverge |
Ah yeah that commit is the same |
mhofman
force-pushed
the
mhofman/8578-upgrade-13-name
branch
from
1508379 to
6426775
Compare
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.
refs: #8578
Description
This prepares the
dev-upgrade-13branch for the next chain software upgrade,agoric-upgrade-13. The branch is based onrelease-mainnet1Bafteragoric-upgrade-12. This PR is the equivalent of #8587 but for the theagoric-upgrade-13release.Security Considerations
None
Scaling Considerations
None
Documentation Considerations
Docker upgrade-test Readme updated with the same changes as #8587
Testing Considerations
Docker upgrade tests coverage should be sufficient
Upgrade Considerations
This sets up the upgrade tests for the next chain software upgrade. Because of the different image naming, cherry-picking from master may require manual conflict resolution.