Labels

• A0-please_review

  A0-please_review

  Pull request needs code review.

• A1-needs_burnin

  A1-needs_burnin

  Pull request needs to be tested on a live validator node before merge. DevOps is notified via matrix

• A2-insubstantial

  A2-insubstantial

  Pull request requires no code review (e.g., a sub-repository hash update).

• A3-in_progress

  A3-in_progress

  Pull request is in progress. No review needed at this stage.

• A4-companion

  A4-companion

  A PR that should be considered alongside another (usually more comprehensive and detailed) PR.

• A5-stale

  A5-stale

  Pull request did not receive any updates in a long time. No review needed at this stage. Close it.

• A6-backport

  A6-backport

  Pull request is already reviewed well in another branch.

• B0-silent

  B0-silent

  Changes should not be mentioned in any release notes

• B1-note_worthy

  B1-note_worthy

  Changes should be noted in the release notes

• C1-low

  C1-low

  PR touches the given topic and has a low impact on builders.

• C3-medium

  C3-medium

  PR touches the given topic and has a medium impact on builders.

• C5-high

  C5-high

  PR touches the given topic and has a high impact on builders.

• C7-critical

  C7-critical

  PR touches the given topic and has a critical impact on builders.

• D1-audited 👍

  D1-audited 👍

  PR contains changes to fund-managing logic that has been properly reviewed and externally audited.

• D2-notlive 💤

  D2-notlive 💤

  PR contains changes in a runtime directory that is not deployed to a chain that requires an audit.

• D3-trivial 🧸

  D3-trivial 🧸

  PR contains trivial changes in a runtime directory that do not require an audit

• D5-nicetohaveaudit ⚠️

  D5-nicetohaveaudit ⚠️

  PR contains trivial changes to logic that should be properly reviewed.

• D9-needsaudit 👮

  D9-needsaudit 👮

  PR contains changes to fund-managing logic that should be properly reviewed and externally audited

• E0-runtime_migration

  E0-runtime_migration

  PR introduces code that might require downstream chains to run a runtime upgrade.

• E1-database_migration

  E1-database_migration

  PR introduces code that does a one-way migration of the database.

• E2-dependencies

  E2-dependencies

  Pull requests that update a dependency file.

• E3-host_functions

  E3-host_functions

  PR adds new host functions which requires a node release before a runtime upgrade.

• E4-node_first_update

  E4-node_first_update

  This is a runtime change that will require all nodes to be update BEFORE the runtime upgrade.

• E5-needs_substrate_pr

  E5-needs_substrate_pr

  This is an issue that needs to be implemented upstream in Substrate.

• F0-breaks_everything

  F0-breaks_everything

  This change breaks the underlying networking, sync or related and thus will cause a fork.

• F1-breaks_authoring

  F1-breaks_authoring

  This change breaks authorities or authoring code.

• F2-breaks_consensus

  F2-breaks_consensus

  This change breaks consensus or consensus code.

• F3-breaks_API

  F3-breaks_API

  This PR changes public API; next release should be major.

• I0-consensus

  I0-consensus

  Issue can lead to a consensus failure.

• I1-panic

  I1-panic

  The node panics and exits without proper error handling.