-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Labels Information
Umcaruje edited this page Sep 13, 2015
·
1 revision
| Basic Labels: | |
|---|---|
| By issue type: |
|
| By issue domain: |
|
| Special Labels: | |
|---|---|
![]() |
For bugs that need a fix ASAP and are blocking regular development. |
![]() |
For poorly written issues that are not understandable / incomplete. |
![]() |
For issues that aren't really issues, but users reaching out for help. |
![]() |
For issues consisting of an amount of smaller issues. |
![]() |
For issues that aren't actually related to LMMS. |
![]() |
For issues that already exist. |
![]() |
For non-reproducible issues. |
![]() |
Valid issues that won't be addressed, for whatever reason. |
If an issue is valid, confirmed, well written, and within the scope of LMMS, it should be labeled with bug or enhancement. If it does not match that criteria, that means its either a support request, invalid, a duplicate or it needs clarification.
What is the order in which issues should be solved?
- Issues with the
criticallabel are of the highest priority and should be solved as soon as possible. - Issues that have a milestone have a higher priority than non-milestoned issues. The lower the milestone version number, the higher the priority.
- Bugs have a higher priority than enhancements.







