Proposal to use the following labels on MRs for throughput tracking
We are in full swing with our throughput chart implementation. To properly categorize MRs we would like to start with the following labels:
- ~bug : MR to resolve a defect/bug in the product
- NEW feature : MR with code for feature work
- security : MR to resolve a security issue
- NEW impediments : MR to address Architecture (examples: MR Refactor, Componentized UI, etc) or Industry (examples: Rails 5 upgrade, BS4 upgrade, ~= TLS upgrades)
cc/ @backend-managers Would like to hear your thoughts on this proposal. We need to start applying these labels ASAP so we can start collecting proper data for throughput tracking.
If you are not familiar with Throughput. Please take a look at gitlab-com/www-gitlab-com!12816 (merged)
Final Proposal
- ~bug
- ~"feature proposal" renamed to feature
- security
- Community contribution
- ~backstage
- undefined
Edited by Dalia Havens