chevdor / cumulus Goto Github PK
View Code? Open in Web Editor NEWThis project forked from paritytech/cumulus
DON'T USE THIS REPO; THIS IS FULL OF TESTS :)
License: GNU General Public License v3.0
This project forked from paritytech/cumulus
DON'T USE THIS REPO; THIS IS FULL OF TESTS :)
License: GNU General Public License v3.0
These checks should be performed on the codebase.
spec_version
has been incremented since theSignedExtension
s have stayedtransaction_version
if not.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)
Ensure that Parity DevOps has run the new release on Westmint and Statemine collators for 12h prior to publishing the release.
Add any necessary assets to the release. They should include:
The release notes should list:
The release notes may also list:
A runtime upgrade must bump the spec number. This may follow a pattern with the
client release (e.g. runtime v12 corresponds to v0.8.12, even if the current
runtime is not v11).
The clients need to be aware of runtime changes. However, we do not want to bump the
spec_version
for every single release candidate. Instead, we can bump the impl
field of the version
to signal the change to the client.
Previous on_runtime_upgrade
functions from old upgrades should be removed.
Ensure that any migrations that are required due to storage or logic changes
are included in the on_runtime_upgrade
function of the appropriate pallets.
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. It also checks if there have been any changes in storage
. In case of a breaking change, increase transaction_version
.
To verify the order has not changed, manually start the following Github Action. It takes around a minute to run and will produce the report as artifact you need to manually check.
To run it, in the Run Workflow dropdown:
master
as defaultwss://kusama-statemine-rpc.paritytech.net
wss://westmint-rpc.polkadot.io
statemine-local
westmint-local
When the workflow is done, click on it and download the zip artifact, inside you'll find an output.txt
file. The things to look for in the output are lines like:
[Identity] idx 28 -> 25 (calls 15)
- indicates the index for Identity has changed[+] Society, Recovery
- indicates the new version includes 2 additional modules/pallets.[Identity] idx 25 (calls 15)
Note: Adding new functions to the runtime does not constitute a breaking change
as long as the indexes did not change.
Note: Extrinsic function signatures changes (adding/removing & ordering arguments) are not caught by the job, so those changes should be reviewed "manually"
The runtime contains proxy filters that map proxy types to allowable calls. If
the new runtime contains any new calls, verify that the proxy filters are up to
date to include them.
Until paritytech#631 is done, running the benchmarks is a manual process:
htop check
cargo build --release --features runtime-benchmarks
nohup ./scripts/benchmarks.sh &
(it will take quite a few hours)scp
from the host to your local machine the weights for Statemine, Westmint and Statemint you'll find in:
/polkadot-parachains/statemine/src/weights
/polkadot-parachains/westmint/src/weights
/polkadot-parachains/statemint/src/weights
This is the release checklist for Polkadot statemine-v99. All following
checks should be completed before publishing a new release. The current release candidate can be
checked out with git checkout release-statemine-v99
These checks should be performed on the codebase prior to forking to a release-
candidate branch.
spec_version
has been incremented since thetransaction_version
if not.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)
Ensure that Parity DevOps has run the new release on Westend, Kusama, and
Polkadot validators for at least 12 hours prior to publishing the release.
Add any necessary assets to the release. They should include:
The release notes should list:
The release notes may also list:
A runtime upgrade must bump the spec number. This may follow a pattern with the
client release (e.g. runtime v12 corresponds to v0.8.12, even if the current
runtime is not v11).
Any previous on_runtime_upgrade
functions from old upgrades must be removed
to prevent them from executing a second time. The on_runtime_upgrade
function
can be found in runtime/<runtime>/src/lib.rs
.
Ensure that any migrations that are required due to storage or logic changes
are included in the on_runtime_upgrade
function of the appropriate pallets.
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. In case
of a breaking change, increase transaction_version
.
To verify the order has not changed, you may manually start the following Github Action. It takes around a minute to run and will produce the report as artifact you need to manually check.
The things to look for in the output are lines like:
[Identity] idx 28 -> 25 (calls 15)
- indicates the index for Identity
has changed[+] Society, Recovery
- indicates the new version includes 2 additional modules/pallets.[Identity] idx 25 (calls 15)
Note: Adding new functions to the runtime does not constitute a breaking change
as long as the indexes did not change.
The runtime contains proxy filters that map proxy types to allowable calls. If
the new runtime contains any new calls, verify that the proxy filters are up to
date to include them.
There are three benchmarking machines reserved for updating the weights at
release-time. To initialise a benchmark run for each production runtime
(westend, kusama, polkadot):
git patch patchfile.patch
Ensure that a release of Polkadot JS API contains any new types or
interfaces necessary to interact with the new runtime.
These checks should be performed on the codebase.
spec_version
has been incremented since theSignedExtension
s have stayedtransaction_version
if not.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)
Ensure that Parity DevOps has run the new release on Westmint and Statemine collators for 12h prior to publishing the release.
Add any necessary assets to the release. They should include:
The release notes should list:
The release notes may also list:
A runtime upgrade must bump the spec number. This may follow a pattern with the
client release (e.g. runtime v12 corresponds to v0.8.12, even if the current
runtime is not v11).
The clients need to be aware of runtime changes. However, we do not want to bump the
spec_version
for every single release candidate. Instead, we can bump the impl
field of the version
to signal the change to the client.
Previous on_runtime_upgrade
functions from old upgrades should be removed.
Ensure that any migrations that are required due to storage or logic changes
are included in the on_runtime_upgrade
function of the appropriate pallets.
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. It also checks if there have been any changes in storage
. In case of a breaking change, increase transaction_version
.
To verify the order has not changed, manually start the following Github Action. It takes around a minute to run and will produce the report as artifact you need to manually check.
To run it, in the Run Workflow dropdown:
master
as defaultwss://kusama-statemine-rpc.paritytech.net
wss://westmint-rpc.polkadot.io
statemine-local
westmint-local
When the workflow is done, click on it and download the zip artifact, inside you'll find an output.txt
file. The things to look for in the output are lines like:
[Identity] idx 28 -> 25 (calls 15)
- indicates the index for Identity has changed[+] Society, Recovery
- indicates the new version includes 2 additional modules/pallets.[Identity] idx 25 (calls 15)
Note: Adding new functions to the runtime does not constitute a breaking change
as long as the indexes did not change.
Note: Extrinsic function signatures changes (adding/removing & ordering arguments) are not caught by the job, so those changes should be reviewed "manually"
The runtime contains proxy filters that map proxy types to allowable calls. If
the new runtime contains any new calls, verify that the proxy filters are up to
date to include them.
Until paritytech#631 is done, running the benchmarks is a manual process:
htop check
cargo build --profile production --locked --features runtime-benchmarks
nohup ./scripts/benchmarks.sh &
(it will take quite a few hours)scp
from the host to your local machine the weights for Statemine, Westmint and Statemint you'll find in:
/polkadot-parachains/statemine/src/weights
/polkadot-parachains/westmint/src/weights
/polkadot-parachains/statemint/src/weights
This is the release checklist for Polkadot statemine-v99. All following
checks should be completed before publishing a new release. The current release candidate can be
checked out with git checkout release-statemine-v99
These checks should be performed on the codebase prior to forking to a release-
candidate branch.
spec_version
has been incremented since thetransaction_version
if not.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)
Ensure that Parity DevOps has run the new release on Westend, Kusama, and
Polkadot validators for at least 12 hours prior to publishing the release.
Add any necessary assets to the release. They should include:
The release notes should list:
The release notes may also list:
A runtime upgrade must bump the spec number. This may follow a pattern with the
client release (e.g. runtime v12 corresponds to v0.8.12, even if the current
runtime is not v11).
Any previous on_runtime_upgrade
functions from old upgrades must be removed
to prevent them from executing a second time. The on_runtime_upgrade
function
can be found in runtime/<runtime>/src/lib.rs
.
Ensure that any migrations that are required due to storage or logic changes
are included in the on_runtime_upgrade
function of the appropriate pallets.
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. In case
of a breaking change, increase transaction_version
.
To verify the order has not changed, you may manually start the following Github Action. It takes around a minute to run and will produce the report as artifact you need to manually check.
The things to look for in the output are lines like:
[Identity] idx 28 -> 25 (calls 15)
- indicates the index for Identity
has changed[+] Society, Recovery
- indicates the new version includes 2 additional modules/pallets.[Identity] idx 25 (calls 15)
Note: Adding new functions to the runtime does not constitute a breaking change
as long as the indexes did not change.
The runtime contains proxy filters that map proxy types to allowable calls. If
the new runtime contains any new calls, verify that the proxy filters are up to
date to include them.
There are three benchmarking machines reserved for updating the weights at
release-time. To initialise a benchmark run for each production runtime
(westend, kusama, polkadot):
git patch patchfile.patch
Ensure that a release of Polkadot JS API contains any new types or
interfaces necessary to interact with the new runtime.
This is the release checklist for Polkadot statemine-v99. All following
checks should be completed before publishing a new release. The current release candidate can be
checked out with git checkout release-statemine-v99
These checks should be performed on the codebase prior to forking to a release-
candidate branch.
spec_version
has been incremented since thetransaction_version
if not.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)
Ensure that Parity DevOps has run the new release on Westend, Kusama, and
Polkadot validators for at least 12 hours prior to publishing the release.
Add any necessary assets to the release. They should include:
The release notes should list:
The release notes may also list:
A runtime upgrade must bump the spec number. This may follow a pattern with the
client release (e.g. runtime v12 corresponds to v0.8.12, even if the current
runtime is not v11).
Any previous on_runtime_upgrade
functions from old upgrades must be removed
to prevent them from executing a second time. The on_runtime_upgrade
function
can be found in runtime/<runtime>/src/lib.rs
.
Ensure that any migrations that are required due to storage or logic changes
are included in the on_runtime_upgrade
function of the appropriate pallets.
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. In case
of a breaking change, increase transaction_version
.
To verify the order has not changed, you may manually start the following Github Action. It takes around a minute to run and will produce the report as artifact you need to manually check.
The things to look for in the output are lines like:
[Identity] idx 28 -> 25 (calls 15)
- indicates the index for Identity
has changed[+] Society, Recovery
- indicates the new version includes 2 additional modules/pallets.[Identity] idx 25 (calls 15)
Note: Adding new functions to the runtime does not constitute a breaking change
as long as the indexes did not change.
The runtime contains proxy filters that map proxy types to allowable calls. If
the new runtime contains any new calls, verify that the proxy filters are up to
date to include them.
There are three benchmarking machines reserved for updating the weights at
release-time. To initialise a benchmark run for each production runtime
(westend, kusama, polkadot):
git patch patchfile.patch
Ensure that a release of Polkadot JS API contains any new types or
interfaces necessary to interact with the new runtime.
This is the release checklist for Statemine v6 and the initial version of
Statemint ๐ (also v6 because of code parity with Statemine).
All following checks should be completed before publishing a
new release of the Statemine runtime. The current release candidate can be
checked out with git checkout release-statemine-v6
.
These checks should be performed on the codebase.
spec_version
has been incremented since theSignedExtension
s have stayedtransaction_version
if not. @NachoPalThe 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)
On top of the regular runtime release process, this release will also need to cover the following points:
setStorage
call for governance to set the initial state Statemint should have after the upgrade (replacing the usual genesis process, but making use of the genesis config) @apopiaksetStorage
calls) @apopiakEnsure that Parity DevOps has run the new release on Westmint and Statemine collators for 12h prior to publishing the release.
Add any necessary assets to the release. They should include:
The release notes should list:
The release notes may also list:
A runtime upgrade must bump the spec number. This may follow a pattern with the
client release (e.g. runtime v12 corresponds to v0.8.12, even if the current
runtime is not v11).
Previous on_runtime_upgrade
functions from old upgrades should be removed.
Ensure that any migrations that are required due to storage or logic changes
are included in the on_runtime_upgrade
function of the appropriate pallets.
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. It also checks if there have been any changes in storage
. In case of a breaking change, increase transaction_version
.
To verify the order has not changed, manually start the following Github Action. It takes around a minute to run and will produce the report as artifact you need to manually check.
To run it, in the Run Workflow dropdown:
master
as defaultwss://kusama-statemine-rpc.paritytech.net
wss://westmint-rpc.polkadot.io
statemine-local
westmint-local
When the workflow is done, click on it and download the zip artifact, inside you'll find an output.txt
file. The things to look for in the output are lines like:
[Identity] idx 28 -> 25 (calls 15)
- indicates the index for Identity has changed[+] Society, Recovery
- indicates the new version includes 2 additional modules/pallets.[Identity] idx 25 (calls 15)
Note: Adding new functions to the runtime does not constitute a breaking change
as long as the indexes did not change.
Note: Extrinsic function signatures changes (adding/removing & ordering arguments) are not caught by the job, so those changes should be reviewed "manually"
The runtime contains proxy filters that map proxy types to allowable calls. If
the new runtime contains any new calls, verify that the proxy filters are up to
date to include them.
Until paritytech#631 is done, running the benchmarks is a manual process:
149.202.69.202
htop check
cargo build --release --features runtime-benchmarks
nohup ./scripts/benchmarks.sh &
(it will take quite a few hours)scp
from the host to your local machine the weights for Statemine, Westmint and Statemint you'll find in:
/polkadot-parachains/statemine/src/weights
/polkadot-parachains/westmint/src/weights
/polkadot-parachains/statemint/src/weights
Ensure that a release of Polkadot JS API can interact with the new runtime (mostly related to RPCs with the new metadata).
A declarative, efficient, and flexible JavaScript library for building user interfaces.
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. ๐๐๐
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google โค๏ธ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.