|
|
|
[[_TOC_]]
|
|
|
|
|
|
|
|
# Global 'dev' labels
|
|
|
|
|
|
|
|
https://lab.civicrm.org/groups/dev/-/labels
|
|
|
|
|
|
|
|
There's a loose convention with prefixing:
|
|
|
|
|
|
|
|
* `sig:*` indicates why something is significant to the product/project (bug, compatibility, performance, usability, etc)
|
|
|
|
* `git:*` indicates a repo where the relevant code lives (civicrm-core, civicrm-packages, etc)
|
|
|
|
* `type:*` indicates a general expectation about resourcing (request, proposal)
|
|
|
|
* `epic:*` indicates that the issue is part of a multifaceted project
|
|
|
|
* `needs:*` indicates what work is currently blocking (e.g. concept approval, steps to replicate, detailed planning, implementation, testing/review)
|
|
|
|
|
|
|
|
There are no labels for fine-grained "priorities" because that's too subjective. However, there are prioritization labels for `priority:critical` and `regression` to signal that an issue merits special consideration in the maintenance/release processes. |
|
|
|
\ No newline at end of file |