-
Notifications
You must be signed in to change notification settings - Fork 380
-
Notifications
You must be signed in to change notification settings - Fork 380
Statemine v6 Release (+ Westmint) #744
Comments
First RC is being prepared in #741 |
We'll want to include #743 |
Keeping track of the extrinc Ordering tests here: Statemine
source: https://github.com/paritytech/cumulus/runs/4179400913?check_suite_focus=true Statemint
source: https://github.com/paritytech/cumulus/runs/4180260451?check_suite_focus=true Westmint
source: https://github.com/paritytech/cumulus/runs/4180272299?check_suite_focus=true |
bumping transaction version: #748 |
This should be skippable now (RPCs are slightly different, since they are not describing yet, but also not critical if not added) - "Polkadot JS |
genesis values WIP here: https://github.com/paritytech/cumulus/tree/apopiak/statemint-genesis-values |
Removed the "Initial Statemine Release" part as we split the Statemine and Statemint releases. |
Statemint released: https://github.com/paritytech/cumulus/releases/tag/statemine-v6.0.1 |
Release Checklist
This is the release checklist for Statemine v6 and the initial version of
Statemint 🎉 (also v6 because of code parity with Statemine).
All following checks should be completed before publishing a
new release of the Statemine runtime. The current release candidate can be
checked out with
git checkout release-statemine-v6
.Runtime Releases
These checks should be performed on the codebase.
spec_version
has been incremented since thelast release for any native runtimes from any existing use on public
(non-private/test) networks.
removed for any public (non-private/test) networks. @apopiak
SignedExtension
s have stayedthe same. Bump
transaction_version
if not. @NachoPalproxy filters. @apopiak
runtime logic. @NachoPal
The following checks can be performed after we have forked off to the release-
candidate branch or started an additional release candidate branch (rc-2, rc-3, etc)
runtime state is correctly updated for any public (non-private/test)
networks.
runtime changes.
All Releases
without issue. @PierreBesson
https://github.com/paritytech/cumulus/releases with relevant release
notes @chevdor
draft-release @chevdor
Notes
Burn In
Ensure that Parity DevOps has run the new release on Westmint and Statemine collators for 12h prior to publishing the release.
Build Artifacts
Add any necessary assets to the release. They should include:
Release notes
The release notes should list:
based on the max priority of any client changes.
srtool
The release notes may also list:
regarding this release
Spec Version
A runtime upgrade must bump the spec number. This may follow a pattern with the
client release (e.g. runtime v12 corresponds to v0.8.12, even if the current
runtime is not v11).
Old Migrations Removed
Previous
on_runtime_upgrade
functions from old upgrades should be removed.New Migrations
Ensure that any migrations that are required due to storage or logic changes
are included in the
on_runtime_upgrade
function of the appropriate pallets.Extrinsic Ordering & Storage
Offline signing libraries depend on a consistent ordering of call indices and
functions. Compare the metadata of the current and new runtimes and ensure that
the
module index, call index
tuples map to the same set of functions. It also checks if there have been any changes instorage
. In case of a breaking change, increasetransaction_version
.To verify the order has not changed, manually start the following Github Action. It takes around a minute to run and will produce the report as artifact you need to manually check.
To run it, in the Run Workflow dropdown:
master
as defaultwss://kusama-statemine-rpc.paritytech.net
wss://westmint-rpc.polkadot.io
statemine-local
westmint-local
When the workflow is done, click on it and download the zip artifact, inside you'll find an
output.txt
file. The things to look for in the output are lines like:[Identity] idx 28 -> 25 (calls 15)
- indicates the index for Identity has changed[+] Society, Recovery
- indicates the new version includes 2 additional modules/pallets.[Identity] idx 25 (calls 15)
Note: Adding new functions to the runtime does not constitute a breaking change
as long as the indexes did not change.
Note: Extrinsic function signatures changes (adding/removing & ordering arguments) are not caught by the job, so those changes should be reviewed "manually"
Proxy Filtering
The runtime contains proxy filters that map proxy types to allowable calls. If
the new runtime contains any new calls, verify that the proxy filters are up to
date to include them.
Benchmarks
Until #631 is done, running the benchmarks is a manual process:
149.202.69.202
htop check
cargo build --release --features runtime-benchmarks
nohup ./scripts/benchmarks.sh &
(it will take quite a few hours)scp
from the host to your local machine the weights for Statemine, Westmint and Statemint you'll find in:/polkadot-parachains/statemine/src/weights
/polkadot-parachains/westmint/src/weights
/polkadot-parachains/statemint/src/weights
Polkadot JS
Ensure that a release of Polkadot JS API can interact with the new runtime (mostly related to RPCs with the new metadata).
The text was updated successfully, but these errors were encountered: