*: Prepare release 0.10.0 #341
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Max Inden <[email protected]>
mxinden
force-pushed
the
release-0.10.0
branch
from
f8a394f to
f9a76da
Compare
lucab
approved these changes
Aug 31, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Follow up to release candidate #340.
We (Parity) have been running
v0.10.0-rc.1on two Kusama (testnetwork) nodes since last week Thursday (27th). I have not seen any abnormal behavior on either of the two. (Ref: paritytech/substrate#6964)With the above in mind I am suggesting to promote the release candidate to the
v0.10.0release. Any objections?