-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Polkadot v0.9.42 Release checklist #7142
Comments
Will this use the new checks added in #6996 ? |
Good question! cc @s3krit |
westend v9401 vs westend v9420
Comparison of the following runtimes:
|
rococo v9401 vs rococo v9420
Comparison of the following runtimes:
|
kusama v9401 vs kusama v9420
Comparison of the following runtimes:
|
polkadot v9401 vs polkadot v9420
Comparison of the following runtimes:
|
bumping |
Yep, when the PR with the new weights gets created, it should run the tests in that PR that compare the weights (and comment as such) |
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
doesn't look like it did |
depends on #7162 |
v0.9.42 is out, see https://github.com/paritytech/polkadot/releases/tag/v0.9.42 |
Release Checklist
This is the release checklist for Polkadot v0.9.42. 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.42
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.Verify previously completed migrations areremoved 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 RCMisc
The text was updated successfully, but these errors were encountered: