-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Polkadot v0.9.30 Release checklist #6069
Comments
Metadata comparison:
|
Metadata comparison:
|
Metadata comparison:
|
Metadata comparison:
|
as suspected by @chevdor this release will also be bumping txver for all runtimes |
bumps pushed |
benchmarks running |
try-runtime #6083 |
weights in #6087 |
The current weights look odd. Checks in progress... |
testing reverts in #6104 |
paritytech/substrate#12425 reverts in substrate |
reverts merged, new rc on the way |
retrying weights in https://gitlab.parity.io/parity/mirrors/polkadot/-/pipelines/219553 |
extrinsic api check on the current rc for double-checking: https://github.com/paritytech/polkadot/actions/runs/3198942363 |
weights on the current rc for double-checking #6123 |
skipping weights |
closing as release was done |
Release Checklist
This is the release checklist for Polkadot v0.9.30. 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.30
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.proxy 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)
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: