Biju -- we have the ability to define components.
It sounds like the consensus is that folks prefer components over
free-form labels.
What are the components that you hoped to find that aren't there?
On 5/13/19 6:31 PM, Biju N wrote:
FYI. There are instances where we don't have "components" which can help
filter a feature for e.g. Quota is a good example. That is a reason for
using labels. This helps in filtering the tickets and get an understanding
of a feature.
On Mon, May 13, 2019 at 5:36 PM Andrew Purtell <[email protected]>
wrote:
I’ve been using components so am accidentally in agreement. Didn’t know
which to use, just picked one. We should document this preference.
On May 13, 2019, at 12:52 PM, Jan Hentschel <
[email protected]> wrote:
Agree with Sean. I would prefer to use labels where we have something,
which is not HBase-specific (such as the “beginner” label), and components
otherwise.
From: Sean Busbey <[email protected]>
Reply-To: "[email protected]" <[email protected]>
Date: Monday, May 13, 2019 at 9:48 PM
To: dev <[email protected]>
Subject: Re: [DISCUSS] Updating categorical info on Jira
labels are shared across the entire jira instance whereas components
are under the control of the project. personally I prefer components.
the only labels I like are when we use "beginner" or if we were to
move away from "Hadoop Flags" to an incompatible change label.
On Mon, May 13, 2019 at 2:34 PM Josh Elser <[email protected]<mailto:
[email protected]>> wrote:
I see BijuN doing a lot of work lately to try to categorize issues
better. Thanks to him for trying to make Jira more usable in that regard!
One concern I have is that we have duplicative categorization:
components and labels. I prefer components as they push us into curated
"names" whereas a label might have skew in capitalization (e.g. "quota",
"Quota", "quotas", "space quota").
What do others think?
--
Sean
