Skip to content
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

Missing labels for new labelling system (round 2) #41

Open
holgerd77 opened this issue Nov 28, 2018 · 5 comments
Open

Missing labels for new labelling system (round 2) #41

holgerd77 opened this issue Nov 28, 2018 · 5 comments

Comments

@holgerd77
Copy link
Member

Some more collection on labels, since I stumbled upon one I would very much like to integrate. Will eventually do a third integration round within a couple of weeks.

@holgerd77
Copy link
Member Author

An eval: needs analysis label would very much complement the current eval type labels.

Sometimes/often issues require a large amount of extra thought/analysis work before one can start to code. A dedicated label makes it more explicit that this is actually a significant separate work step before coding (which can also very well be taken on by a different person). This should to some extend ease the path towards the final implementation.

@holgerd77
Copy link
Member Author

holgerd77 commented Sep 2, 2020

Sometimes missing effort: E0 minutes and effort: E5 years

Use case example for effort: E0 minutes: ethereumjs/ethereumjs-monorepo#912

@ryanio
Copy link
Contributor

ryanio commented Sep 2, 2020

Suggestion: PR: breaking change

@holgerd77
Copy link
Member Author

Missing a type: maintenance label, example case: https://github.com/ethereumjs/ethereumjs-client/issues/149

@evertonfraga
Copy link
Contributor

I have opened a PR with @holgerd77 's new type label.

@ryanio how about we use it like type: breaking change? Because it doesn't quite fit on the PR states category.

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

No branches or pull requests

3 participants