-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create new deprecation
label
#28
Comments
Merged
Might be fixed by #29 |
@juangirini I've already included the deprecation label on the list (see |
Merged
Yeah it is already there, I think this should be closed. |
Closing this to have a unified thread on paritytech/substrate#29 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Despite the efforts for reducing the amount of labels I believe we need to create a new one that indicates a special kind of issue, which is a
deprecation
issue.This is why I believe we need a new label: we are creating a new deprecation process, in which created issues need to follow a special flow. As you can see in that linked issue, this flow is different because deprecating a feature requires some async events, such as updating the documentation or actually removing the feature.
Currently we are relying in keywords to filter such issues, but obviously this isn't optimal.
The text was updated successfully, but these errors were encountered: