-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Polkadot v0.9.19 Release checklist #5288
Comments
Metadata comparison:
|
Metadata comparison:
|
Metadata comparison:
|
Metadata comparison:
|
Milestone checks: ✅ #5182 is in release-v0.9.19 via commit(s): ✅ #5079 is in release-v0.9.19 via commit(s): ✅ #5032 is in release-v0.9.19 via commit(s): ✅ #5016 is in release-v0.9.19 via commit(s): ✅ #5000 is in release-v0.9.19 via commit(s): ✅ #4809 is in release-v0.9.19 via commit(s): ✅ #3889 is in release-v0.9.19 via commit(s): ⛔ No commit related to #5045 found, check #5045 |
This comment was marked as outdated.
This comment was marked as outdated.
rel #5302 |
rel #5319 |
runtime migration testing in #5322 |
Release Checklist
This is the release checklist for Polkadot v0.9.19. 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.19
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.
Verify benchmarks have been updated for any modifiedruntime 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
The text was updated successfully, but these errors were encountered: