Skip to content

Introduce new labels to define the priority of an issue: high, normal and low #245

@patricekrakow

Description

@patricekrakow

In order to ease the management of our issues, we can introduce new labels: high, normal and low.

As we start to have many labels, we can also introduce the following naming convention that would define label groups (which is a notion that does not exist natively in GitHub): <label-group>:<label-name>.

Issue priority group:

  • prio:low
  • prio:normal
  • prio:high

source: https://softwareengineering.stackexchange.com/a/132320

We should also probably re-discuss/re-name our current label in order to adopt this new naming convention.

Metadata

Metadata

Assignees

No one assigned

    Labels

    MUST BE DISCUSSEDMust be discussed during the next CWG meeting

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions