visortelle commented on issue #22277:
URL: https://github.com/apache/pulsar/issues/22277#issuecomment-2003677752
> `flacky` --> `flaky`
thanks, good catch 👍
> The only thing I don't know, in general, is how labels are used, in real
life.
I can share how I see it:
- We usually prioritize bugs over features. Of course with reasonable
limits. Adding a label to bugs makes it easy to filter them and answer a
question about what to do next.
- Non-critical bugs and nice-to-have features that are planned, but not
prioritized we can mark as `good-first-issue` and/or `help-wanted` to give new
contributors a pool of issues they can take from.
- I'm not a fan of closing `stale` issues that are neither `resolved` nor
`not planned`. It looks like it is hiding existing problems under the sofa.
- The `area/*` labels allow a person who is interested or has good knowledge
in a specific area to filter issues related to this area to get an overview of
existing problems, what is work in progress, and retrospection of what has
happened in this area. If someone is good at writing documentation.
@asafm you could simply filter by `area/metrics` to get an overview of all
the issues and PRs related to the topic you're interested in. It simplifies
navigation when you have thousands of issues.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
