From 3f0d689877ecd2dd1b521f25b772159ec3a4ebb5 Mon Sep 17 00:00:00 2001 From: Xavier Lau Date: Sun, 22 Dec 2024 20:15:22 +0800 Subject: [PATCH] Amend PRR --- applications/polkadot-runtime-releaser.md | 10 +++------- 1 file changed, 3 insertions(+), 7 deletions(-) diff --git a/applications/polkadot-runtime-releaser.md b/applications/polkadot-runtime-releaser.md index 3beae2561e3..ff3f6e15e24 100644 --- a/applications/polkadot-runtime-releaser.md +++ b/applications/polkadot-runtime-releaser.md @@ -23,10 +23,6 @@ Especially to the new teams, they might not have enough experience to handle it. - The rustc/OS version affects the compiled artifacts. - There are also some unclear things of the srtool. - E.G. https://substrate.stackexchange.com/questions/11686/getting-error-rust-nightly-not-installed-when-starting-an-srtool-container-to-bu​a -- When to notify the community to upgrade the node? - - Collator/Validator nodes should be upgraded first. - - RPC suppliers should be upgraded later. - - I saw some EVM RPCs require the runtime version to be equal to the node version. - How to host a wasm-override repository for the community? - Debug log WASM. - We always use `sp-api/disable-logging` in the release build, so no more detail logs in the general runtime. @@ -60,8 +56,8 @@ PRR will supply these components, which will all be hosted in one repository. - A GitHub Action to response the try-runtime. (Users can comment something like `/bot try-runtime ` under a release PR to trigger this action.) - A GitHub Action to build the release runtime. - A GitHub Action to notify release repository there is a new release that release repository can start preparing the override WASMs. -- A GitHub Action and a tool to monitor the on-chain runtime version and compare it with the release runtime version to trigger the release on the release repository. - A tool to build and manage the override WASMs. +- A tool to inspect the basic information from the WASM file. | GitHub Action | Trigger | Output | | --------------: | -------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------- | @@ -130,13 +126,13 @@ If they contain no activity, references to projects hosted elsewhere or live are | Number | Deliverable | Specification | | -----: | ----------------------------- | --------------------------------------------------------------------------------------------------------------------- | | 0a. | License | GPLv3 | -| 0b. | Documentation | There will be a guide to tell people how to use this and inline docs will cover core functionalities. | +| 0b. | Documentation | There will be a guide to tell people how to use this and inline docs will cover core functionalities. | | 0c. | Testing guide | There will be a guide and a demo repository to tell the auditor how to run the tests. All components will be covered. | | 1. | Try-runtime CI | Comment on a release PR and see the try-runtime result. | | 2. | Release CI | Build and release the deterministic runtime and the node files. | | 3. | WASM override tool | It can build the specify feature WASM in one step and manage them well in the corresponding folder. | | 4. | WASM override CI | Listen for build requests from the release CI. | -| 5. | Version compare tool | It can retrieve the on-chain runtime version and compare it with the latest GitHub tag. | +| 5. | WASM info inspect tool | It can retrieve the on-chain runtime version and compare it with the latest GitHub tag. | | 6. | Release repository release CI | Based on the version comparison tool result, proceed to release the new version in this repository. | | 7. | Releases | GitHub release. |