Manta v4.0.3 Release checklist #1034
Labels
A-calamari
Area: Issues and PRs related to the Calamari Runtime
C-enhancement
Category: An issue proposing an enhancement or a PR with one
Release Checklist
Most of the following checks should be completed before officially publishing the new release
of the Calamari/Manta runtime or client. Some need to be completed after the new code is deployed.
These checks should be performed on the codebase prior to freezing our release candidate:
manta
should happen until told otherwiserelease-vX.Y.Z
orrelease-vX.Y.Z-something
( something could be e.g.alpha
orrc1
). Substitute X Y Z with the release version number.version
has been bumped from previous release.spec_version
has been incremented since thelast release for any native runtimes from any existing use on public
(non-private/test) networks. If the runtime was published (release or pre-release), either
the
spec_version
orimpl
must be bumped.the same. Bump
transaction_version
if not.runtime logic.
try-runtime
, if any.POLKADOT_BINARY
and_BINARY
and update themdev-tools
repomanta
branch commit for the tag, NOT arelease-
or other branchDeploy to internal testnets ( fast runtime )
runtime changes.
Deploy to public testnet
Deploy to mainnet
Before Runtime Upgrade Vote
authorize_upgrade
.During Runtime Upgrade Vote
manta
, include the block number the upgrade is enacted!Notes
Release Notes
The release notes MUST contain:
based on the max priority of any client changes.
The release notes MAY also list:
regarding this release
Spec Version
A runtime upgrade must bump the spec number. This may follow a pattern with the
client release
Extrinsic Ordering
Offline signing libraries depend on a consistent ordering of call indices and
functions. Compare the metadata of the current and new runtimes and ensure that
the
module index, call index
tuples map to the same set of functions. To generate a diff report you can do the following:Run workflow
drop-down menu.output.txt
are lines like:[Identity] idx 28 -> 25 (calls 15)
- indicates the index forIdentity
has changed[+] Society, Recovery
- indicates the new version includes 2 additional modules/pallets.[Identity] idx 25 (calls 15)
In case of a breaking change, bump the
transaction_version
.Note: Adding new functions to the runtime does not constitute a breaking change
as long as the indexes did not change.
Benchmarks
There is a manually deployed github action that runs all benchmarks on a bare-metal AWS machine. In order to use go to :
Run workflow
drop-down menu.dolphin-dev
,calamari-dev
,manta-dev
.Security Audit
Before release, run a
Security Audit
Run workflow
drop-down menu.The text was updated successfully, but these errors were encountered: