This repository has been archived by the owner on Nov 15, 2023. It is now read-only.
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.
EPM and staking events improvement #13035
EPM and staking events improvement #13035
Changes from 1 commit
45940b2
9d1a25f
73dcbd6
1685ac1
d682484
dd45479
26f7f65
641b287
ca10f7b
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
These changes might break some UIs depending on these events. May be we should label it as
breaking changes
(E5
?,B7
) with some release notes in description.@kianenigma might have better insights.
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.
I don't think any UI reads these events, so it should be okay.
Nonetheless, I would love to see Ankan's suggestions in PRs that actually do break UIs that we care about.
The broader meta-discussion here is what degree of release-note do we want to have for breaking frame changes.
I think there is a LOT LOT more that we can do here, but the current labels are barely enough to reflect changes that are relevant to parachain teams and polkadot, and for this audience I don't think this matters.
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.
hi,
currently the only thing you can do to highlight a code change on the release notes is elevating its upgrade criticality with the
C*
labels. This will change though, we're slowly implementing new labels on polkadot/substrate/cumulus that have a clear description and in future theC*
labels should be used in combination with other labels so that you can distinguish what it is about upfront. Here is the documentation of the new labels explaining how they should be used: https://github.com/paritytech/labels/blob/main/docs/doc_cumulus.md