Open muharem opened 1 year ago
The transaction_version check is semi-automated and a newer version of that check is being worked on by @chevdor (this is the metadata differ that only needs the runtimes as inputs).
Yes, I am actually working on an option that may even allow handling the transaction_version
topic in a fully automated way.
The document is Work In Process and can be altered.
Problem
Parachains runtime release takes up to 2 weeks to prepare and publish.
Context
Parachains runtime release is semi-automated and takes up to 2 weeks to prepare and publish. Most of this time are manual checks, fixes, backports, weight calculation reruns. The target release cadence is one release every third week (same as relay chains / polkadot repo) which brings a manpower intensive release process.
In this document we will gather all related issues, and use the document as a reference for the problem.
Goals
Known issues
Release steps completion notifications
To allow all interested parties at any time to check the current release status, we want to notify via a message to a dedicated Element room about every release steps completion.
Notifications:
spec_versions
bump PR created (when automated)transaction_version
bump PR created (when automated)