Skip to content
This repository has been archived by the owner on May 22, 2023. It is now read-only.

Backport sp-staking from polkadot-v0.9.36 #190

Open
wants to merge 2 commits into
base: dev-cere
Choose a base branch
from

Conversation

khssnv
Copy link
Member

@khssnv khssnv commented Feb 14, 2023

This update introduces sp-staking-backport create with sp-staking backported from substrate polkadot-v0.9.36 branch.

The only change applied to the original crate is a deletion of a line staking/src/lib.rs#L194 incompatible with the current version of sp-core create in dev-cere and not required for a purpose of the backport.

@khssnv khssnv force-pushed the feature/backport-sp-staking-from-polkadot-0.9.36 branch from eea1074 to 7cde43a Compare February 24, 2023 06:24
@khssnv khssnv changed the title Backport sp-staking from polkadot-0.9.36 Backport sp-staking from polkadot-v0.9.36 Feb 24, 2023
@@ -0,0 +1,29 @@
[package]
name = "sp-staking-backport"

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do you see any possible issues with renaming it back to sp-staking after we reach the Substrate target version? If yes, can we somehow prevent them now?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

When the version from polkadot-v0.9.36 branch reached, the sp-staking-backport crate should be removed and all references to sp-staking-backport should be replaced with sp-staking. I expect a quick and simple update.

@@ -5,6 +5,10 @@ All notable changes to this project will be documented in this file.
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).

## [vNext]

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We have two [vNext] sections now

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we keep them separated or merge them, @AndreiNavoichyk?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants