Labels
A variety of labels is used in this repo to represent different states and concepts related to the issue they're assigned to. There are several sets of labels, which are used to describe an issue, it's complexity and state it is in. The list below details out all those sets and the labels in them:
The following labels represent all the states of an issue during its lifecycle:
Assigned to the issues which require investigation, and it's not clear how the team will proceed further. State of the issue will potentially be clarified after the investigation is done.
Applied to issues which require wider discussions before a decision can be made regarding next steps
Applied to the issues to indicate that the observed behavior is actually intentional. Hence the behavior is by-design.
Indicates that all the necessary information about how to proceed further has been collected, and the issue is ready to be handled.
Issues with this label are available for the community members to handle.
Indicates that a spec defining user experience is required
Indicates that a design for the solution is required
Applied to an issue when something else is pending to be ready for this work, and that's not the case.
This label is used to replace an already applied 1 - Ready label. Applied as soon as an engineer or the person who actually handles the issue (fixes a bug or implements a feature) starts working on it.
Applied, when the pending work represented by the issue is completed. This label replaces 2 - Working label, if such was applied to the issue.
Applied to an issue which describes a bug, which the team couldn't reproduce. These issues will usually be closed.
Indicates that the fix for the issue requires a breaking change.
Indicates an issue, which represents an incorrect behavior of the framework.
Indicates an issue, which represents introduction of a new behavior.
Indicates a relatively big chunk of work to introduce a feature
Indicates an internal area of the framework, which the issue is going to have impact on
Indicates that the issue represents a discussion around certain topic, usually aimed to make certain decision
Indicates that the work involved is related to documentation.
Applied to issues, which represent same work as some other issue already does.
Indicates, that the cause for the observed behavior is not related to the code in this repository and is because of some other factor.
Indicates an issue which is directly mapped with planning work
Indicates feedback regarding a specific area of the framework
The following labels are used to cost the issues in terms of how big or small the work involved is
Almost no time is required to complete the work. These are usually tracking issues.
The work involved will take up to half a day
The work required to complete the issue will take up to two days
The work required to complete the issue will take from 3-5 days
The work required to complete the issue will take from 4-10 days
The work required to complete the issue will take more than 10 days to complete.
Blocks a critical product path. Must be handled immediately
Must be handled in a reasonable time
Preferably should be handled during the milestone.
Represents a low-priority issue. Handle if time allows.