handbook single-source-of-truth for feature vs bug issues
Why is this change being made?
review app links
We define feature and bug in:
- In the label description (bug, feature)
- Within the engineering part of the handbook
Plus they're mentioned in the development docs without any definitions.
Label descriptions appear in mouse-over, but they're necessarily brief, and it's hard to link to them: label edit pages (bug, feature) return a 404 for anyone outside GitLab.
Goal of this MR is to create a single source of truth for when something is a bug or feature request, and put it in the context of iteration. When a customer or user wants to to understand the distinction, we can then be transparent about the criteria.
To do
-
fix the broken links to the new page -
link from development docs (Separate MR for the GitLab repository required) -
link from labels (manual change)
reference: CEO call 2020-03-04 google doc (internal), youtube
Does this MR meet the acceptance criteria?
Assign to DRI
-
Did you assign this change to the correct DRI of the page or information you are changing?
Conformity
-
Added description to this MR explaining the reasons for the proposed change, per say-why-not-just-what