summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJob van der Voort <jobvandervoort@gmail.com>2016-05-17 14:57:58 -0500
committerJob van der Voort <jobvandervoort@gmail.com>2016-05-17 14:57:58 -0500
commite093771633b9861c90fb1a4a7e5ff69a455ebb8a (patch)
treedb4ce6d789cea4ab202918b434fb5fceff1f9295
parent1fdbf0dd24891ef81a8f30c1651fda9c10c23368 (diff)
downloadgitlab-ce-product-md.tar.gz
note on labelsproduct-md
-rw-r--r--PRODUCT.md5
1 files changed, 5 insertions, 0 deletions
diff --git a/PRODUCT.md b/PRODUCT.md
index edbe945b647..8fe1991c888 100644
--- a/PRODUCT.md
+++ b/PRODUCT.md
@@ -47,3 +47,8 @@ An engineer working on an issue is not expected to first read through a long com
## Scheduling issues
Scheduling issues happens according to milestones. This has to be done in close collaboration with engineering.
+
+## Labels
+
+Issues should have relevant labels applied. For most changes, this would be
+~"feature proposal". See [PROCESS](PROCESS.md) for more details.