12 Matching Annotations
- May 2021
-
github.com github.com
Tags
Annotators
URL
-
- Apr 2021
-
github.com github.com
-
Actually, I've decided to stop using labels for a while. A "bug" label gives the impression that someone else is going to fix the problem. We don't have enough volunteers for that (new contributors welcome!). I try to help people working on issues, though. I've spent many hours on this one.
-
- Nov 2020
-
github.com github.com
-
priority: 5 (nice to have) semver: Minor severity: 5 (confusing) type: Feature
-
- Oct 2020
-
github.com github.com
-
first sighting: use of superscripts like this
I like it. Nice and concise and understandable.
- s¹  critical
- s²  important
- s³  nice to have
- s⁴  low
- s⁵  inconvenient
But in other cases, the abbreviation is quite unclear and ambiguity:
Like, what does "pr" mean in these cases?
priority? Doubt it.
- pr¹  chore
- pr²  docs
- pr³  feature
- pr⁴  fix
- pr⁵  performance
- pr⁶  refactor
- pr⁷  style
Pull Request? Doubt it. But maybe?
For axes that are quantifiable, like severity, using a number makes sense. But what benefit is there in including a number in these (platform?) labels?:
- p¹ ⋅ browser
- p² ⋅ linux
- p³ ⋅ mac
- p⁴ ⋅ windows
I think this would have been better and clearer (in that fewer people would be like huh? and wonder what it means):
- platform: browser
- platform: linux
- platform: mac
- platform: windows
-
- May 2020
-
gitlab.com gitlab.com
-
-
Priority labels
-
Type labels are very important. They define what kind of issue this is. Every issue should have one and only one.
-
Sometimes it's useful to refine the type of an issue. In those cases, you can add facet labels.
-
Labeling is a task for everyone.
-
-
github.com github.com
-
Labeling Issues
-
-
gitlab.com gitlab.com
Tags
Annotators
URL
-
-
gitlab.com gitlab.com
Tags
Annotators
URL
-