This repository was archived by the owner on Nov 15, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Polkadot v0.9.43 Release checklist #7286
Comments
backported paritytech/substrate@0cf64f8 per @acatangiu request |
diff polkadot
|
diff kusama
|
diff westend
|
diff rococo
|
Given that the |
|
westend deployment https://github.com/paritytech/devops/issues/2620 |
westend fell over, probably have to backport #7340 or similar edit: backported |
westend is back up, waiting on deployment |
westend deployed |
released |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Release Checklist
This is the release checklist for Polkadot v0.9.43. 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.43
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)
runtime state is correctly updated for any public (non-private/test)
networks.
runtime changes.
Check with the Signer's team to make sure metadata update QR are lined upAll 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: