-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Polkadot v0.9.31 Release checklist #6169
Comments
Metadata comparison:
|
Metadata comparison:
|
Metadata comparison:
|
Metadata comparison:
|
the transaction version has decreased in these outputs because the last increase was not backported. |
i've also made a note to backport the versions from this release once merged to make sure master is in sync again. |
benchmarks running in https://gitlab.parity.io/parity/mirrors/polkadot/-/pipelines/222212 |
weights in #6173 |
try-runtime testing in #6175 |
backports to master in #6176 |
try-runtime passes on kusama https://gitlab.parity.io/parity/mirrors/polkadot/-/jobs/1974761 |
We have about 19 migrations across the four runtimes in this release, maybe we can do some |
|
|
|
|
new benches with substrate fix https://gitlab.parity.io/parity/mirrors/polkadot/-/pipelines/222896 |
weights (attempt 2) #6189 |
migration cleanup #6205 |
pulled in #6214 |
waiting on info about paritytech/polkadot-sdk#758 |
released |
Release Checklist
This is the release checklist for Polkadot v0.9.31. 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.31
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. -> d681c7cremoved for any public (non-private/test) networks. -> 3117b81
the same. Bump
transaction_version
if not. -> 50c541cproxy filters. -> does not need to be checked anymore, should be dropped from checklist template
runtime logic. -> 6476ab8
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 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: