-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Polkadot v0.9.22 Release checklist #5496
Comments
Metadata comparison:
|
Metadata comparison:
|
Metadata comparison:
|
Metadata comparison:
|
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
These are the correct benchmarks that have already been running for a while: |
This comment was marked as outdated.
This comment was marked as outdated.
Milestone checks:✅ #5511 is in release-v0.9.22 via commit(s): ✅ #5505 is in release-v0.9.22 via commit(s): ✅ #5447 is in release-v0.9.22 via commit(s): ✅ #4344 is in release-v0.9.22 via commit(s): ⛔ No commit related to #4971 found, check #4971 Comment: |
RuntimesThe Westend runtime upgrade to v9220 went fine and the network looks good (see metrics below). The Rococo runtime upgrade to v9220 (done before Westend) went fine as well. Node burninsThe Westend burnin is running for a few hours only and looks very good already. All the nodes are reporting metrics: The number of INFO /h is within specs and steady: The reported WARN is very low with the usual peak during upgrade: Similarly, the ERROR /h increased during upgrade but stabilized shortly after: The production rate is within standards (besides the wrong units/title :): |
A note that we will switch nodes to ParityDB and be able to gether more metrics for those. |
@chevdor can you also update some RPC nodes on westend as a burn in? I don't know what's a good number maybe 2/3 of the RPC nodes? |
Log collection is down atm on Westend and I usually filter the RPC nodes out but I can check once we get logs in again. |
Release Checklist
This is the release checklist for Polkadot v0.9.22. 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.22
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.
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. => [don't merge] try runtime testing #5512 (comment)
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: