This repository was archived by the owner on Apr 2, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 5
Issue Tracking
Oscar Olazabal edited this page Oct 2, 2019
·
11 revisions
Issues are classified into following labels. When creating an issue, one must ensure it is assigned to one of these labels. Below are some of the available labels and their descriptions. Please refer to the repository's label page to see all available labels.
| Label | Description |
|---|---|
milestone plan |
Outline of items from the roadmap that are being addressed. |
feature |
Enhancement that is to be added to the project. |
feature-request |
Request to change or to add new feature. |
backend |
Issue that relates to a backend implementation. |
frontend |
Issue that relates to a frontend implementation. |
bug |
Indicator that a feature has a defect |
bug fix |
Implementation that fixes a defect. Typically used om a pull request. |
done |
Feature or bug fix has been completed. |
wont do |
Feature that will not be worked on. |
duplicate |
This issue already exists. |
question |
Question regarding an existing feature or issue. |
When creating an issue that requires an implementation, it is good idea to assign it a difficulty. Leverage the following labels
| Label | Description |
|---|---|
easy |
Easy issue to be worked on. |
medium |
Mid difficultly issue to be worked on. |
challenging |
Challenging issue to be worked on. |
In addition to labeling the issue, please be sure to associate the issue with its associated milestone (if it has one).