diff options
| author | Douwe Maan <douwe@gitlab.com> | 2016-03-01 16:55:34 +0000 |
|---|---|---|
| committer | Douwe Maan <douwe@gitlab.com> | 2016-03-01 16:55:34 +0000 |
| commit | 90ced487f2e8a6252864f9ac8821c2de06be9ced (patch) | |
| tree | 0c57ed316c8f815118f03f260aea3f049ebb3acc | |
| parent | 9b3c1a8c4f53d97ef46e82706dc159756b354ad3 (diff) | |
| parent | b7e26e9c47bb16ef964ed08ccf1132a589fde9fd (diff) | |
| download | gitlab-ce-90ced487f2e8a6252864f9ac8821c2de06be9ced.tar.gz | |
Merge branch 'add_customer_label' into 'master'
Add customer label explanation and change label references to markdown
Add customer label plus change valid labels to markdown format so they render.
The unchanged labels do not have actual/valid labels behind them. We should consider removing them since they're obviously not used.
cc/ @sytses @dzaporozhets @DouweM What do you think about removing the unused labels?
Label names are now rendered
See merge request !2972
| -rw-r--r-- | PROCESS.md | 19 |
1 files changed, 8 insertions, 11 deletions
diff --git a/PROCESS.md b/PROCESS.md index 5f4d67bc10e..54ebe11d5a0 100644 --- a/PROCESS.md +++ b/PROCESS.md @@ -36,18 +36,15 @@ The most important thing is making sure valid issues receive feedback from the d Workflow labels are purposely not very detailed since that would be hard to keep updated as you would need to re-evaluate them after every comment. We optionally use functional labels on demand when want to group related issues to get an overview (for example all issues related to RVM, to tackle them in one go) and to add details to the issue. -- *Awaiting feedback*: Feedback pending from the reporter -- *Awaiting confirmation of fix*: The issue should already be solved in **master** (generally you can avoid this workflow item and just close the issue right away) -- *Attached MR*: There is a MR attached and the discussion should happen there - - We need to let issues stay in sync with the MR's. We can do this with a "Closing #XXXX" or "Fixes #XXXX" comment in the MR. We can't close the issue when there is a merge request because sometimes a MR is not good and we just close the MR, then the issue must stay. -- *Developer*: needs help from a developer -- *UX* needs needs help from a UX designer -- *Frontend* needs help from a Front-end engineer -- *Graphics* needs help from a Graphics designer -- *up-for-grabs* is an issue suitable for first-time contributors, of reasonable difficulty and size. Not exclusive with other labels. -- *feature proposal* is a proposal for a new feature for GitLab. People are encouraged to vote +- ~"Awaiting Feedback" Feedback pending from the reporter +- ~UX needs help from a UX designer +- ~Frontend needs help from a Front-end engineer +- ~up-for-grabs is an issue suitable for first-time contributors, of reasonable difficulty and size. Not exclusive with other labels. +- ~"feature proposal" is a proposal for a new feature for GitLab. People are encouraged to vote in support or comment for further detail. Do not use `feature request`. - +- ~bug is an issue reporting undesirable or incorrect behavior. +- ~customer is an issue reported by enterprise subscribers. This label should +be accompanied by *bug* or *feature proposal* labels. Example workflow: when a UX designer provided a design but it needs frontend work they remove the UX label and add the frontend label. ## Functional labels |