-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Polkadot v0.9.37 Release checklist #6540
Comments
weights in #6546 |
kusama v9360 vs kusama v9370
Comparison of the following runtimes:
|
polkadot v9360 vs polkadot v9370
Comparison of the following runtimes:
|
westend v9360 vs westend v9370
Comparison of the following runtimes:
|
rococo v9360 vs rococo v9370
Comparison of the following runtimes:
|
bumped txver in rc3 |
Hey could you please point me to the try-runtime CI job? @coderobe |
westend upgrade in https://github.com/paritytech/devops/issues/2259 |
which try-runtime CI job do you mean, @ggwpez ? |
Yea that is kind of the problem. If does happen automatically as soon as the runtime-migration label is present. BUT the CLI was changed and the actual checks do not run 🤦 The stupid thing is that that if we enable the checks on every MR CI, then there is a chance that we cannot make it green since Polkadot did not yet execute the runtime update and the |
Release Checklist
This is the release checklist for Polkadot v0.9.37. All following
checks should be completed before publishing a new release of the
Polkadot/Kusama/Westend/Rococo runtime or client. The current release candidate can be
checked out with
git checkout release-v0.9.37
Runtime Releases
These checks should be performed on the codebase prior to forking to a release-
candidate branch.
spec_version
has been incremented since thelast release for any native runtimes from any existing use on public
(non-private) networks. If the runtime was published (release or pre-release), either
the
spec_version
orimpl
must be bumped.removed for any public (non-private/test) networks.
the same. Bump
transaction_version
if not.Verify new extrinsics have been correctly whitelisted/blacklisted forproxy filters.
runtime logic.
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)
Verify new migrations complete successfully, and theruntime state is correctly updated for any public (non-private/test)
networks.
runtime changes.
All Releases
Check that the new client versions have run on the networkwithout issue for 12+ hours on >75% of our validator nodes.
https://github.com/paritytech/polkadot/releases with relevant release
notes
draft-release
freenotes
were added into the release branch after the latest generated RCThe text was updated successfully, but these errors were encountered: