pezkuwichain/pezkuwi-subxt
1
0
Fork 0
mirror of https://github.com/pezkuwichain/pezkuwi-subxt.git synced 2026-06-09 20:11:09 +00:00
Code Issues Packages Projects Releases Wiki Activity

Clarification on the use of vstaging (#7359)

Browse Source 
* Clarifications on vstaging.

* Typos.

---------

Co-authored-by: eskimor <eskimor@no-such-url.com>
This commit is contained in:
eskimor
2023-06-21 12:23:03 +02:00
committed by GitHub
parent 5ac7b32ca9
commit a25b871a16
1 changed files with 6 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
polkadot/primitives/src/runtime_api.rs
+6 -2
View File
@@ -92,8 +92,12 @@
//! Let's introduce two types of `ParachainHost` API implementation:
//! * stable - used on stable production networks like Polkadot and Kusama. There is only one
//! stable API at a single point in time.
//! * staging - used on test networks like Westend or Rococo. Depending on the development needs
//! there can be zero, one or multiple staging APIs.
//! * staging - methods that are ready for production, but will be released on Rococo first. We can
//! batch together multiple changes and then release all of them to production, by making staging
//! production (bump base version). We can not change or remove any method in staging after a
//! release, as this would break Rococo. It should be ok to keep adding methods to staging
//! across several releases. For experimental methods, you have to keep them on a separate branch
//! until ready.
//!
//! The stable version of `ParachainHost` is indicated by the base version of the API. Any staging
//! method must use `api_version` attribute so that it is assigned to a specific version of a