Skip to content
This repository was archived by the owner on Nov 15, 2023. It is now read-only.
This repository was archived by the owner on Nov 15, 2023. It is now read-only.

Parachains runtime release process  #1657

Open
@muharem

Description

@muharem

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

  • parachains runtime release takes up to 3 days;
  • issue-free release builds;
  • well defined and transparent release process:
    • every step is documented;
    • the progress (ex. release branch creation) can be followed by team members (ex. message notifications in matrix);

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:

  • runtime spec_versions bump PR created (when automated)
  • runtime transaction_version bump PR created (when automated)
  • release branch created
  • weights generated (link to the PR)
  • integration tests completed
  • release candidate built
  • release published

Metadata

Metadata

Assignees

No one assigned

    Labels

    A3-in_progressPull request is in progress. No review needed at this stage.T9-releaseThis PR/Issue is related to topics touching the release notes.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions