-
Notifications
You must be signed in to change notification settings - Fork 3
Backport sp-staking from polkadot-v0.9.36 #190
base: dev-cere
Are you sure you want to change the base?
Conversation
eea1074 to
7cde43a
Compare
| @@ -0,0 +1,29 @@ | |||
| [package] | |||
| name = "sp-staking-backport" | |||
There was a problem hiding this comment.
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?
There was a problem hiding this comment.
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.
| 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] |
There was a problem hiding this comment.
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
There was a problem hiding this comment.
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?
This update introduces
sp-staking-backportcreate withsp-stakingbackported 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-corecreate indev-cereand not required for a purpose of the backport.