Review Priority Label Guidelines
We should document a rough set of guidelines for what Review Priority label for the Community contribution's to use.
Proposal
We'll add this to CONTRIBUTING.md as it's the intended entry point for anyone looking to contribute to the project.
Label | Meaning | Use Cases |
---|---|---|
ReviewP1 | Highest priority to review | Indicates an MR that might solve an urgent pain point for users, contributes to the strategic direction of the runner development as laid out by the Product team, or fixes a critical issue. We maintain a hard cap on the number of contributions marked ReviewP1 at which is currently set at 3 |
ReviewP2 | Default priority to review | All incoming MRs should be defaulted to this |
ReviewP3 | Lowest priority to review | WIP MRs, feature enhancements that only appear to serve a small number of users |
Thoughts @brendan @tmaczukin @steveazz @rpaik ?
Edited by Elliot Rushton