Krita/Docs/BugsPriorityHowto: Difference between revisions

From KDE Community Wiki
< Krita‎ | Docs
No edit summary
Line 1: Line 1:
== Dmitry's Wokrboard howto ==
== Bugs Priority HOWTO ==
 
We have quite a lot of bugs and wishes on bugzilla, so we need to decide, what bugs are real priority, and which are not. Here is a proposal of 


There are four columns for bugs in [https://phabricator.kde.org/project/board/9/ this workboard] on the phabricator.
There are four columns for bugs in [https://phabricator.kde.org/project/board/9/ this workboard] on the phabricator.

Revision as of 13:33, 24 January 2016

Bugs Priority HOWTO

We have quite a lot of bugs and wishes on bugzilla, so we need to decide, what bugs are real priority, and which are not. Here is a proposal of

There are four columns for bugs in this workboard on the phabricator.

  • Needs Info — the bug has been checked/answered by a deveoper, but it needs more info from the community. It might need some more details, comments or GUI designs. After staying in this column for too long, it might be deleted.
  • Minor Fix — quick reproducible bug that can be fixed in spare time in a couple of hours.
  • Triaged — usual bugs that should be worked on. Preferably, the bug should be reproducible. If not, it will be moved back to Needs Info column. The bugs at the top has higher priority than the ones at the bottom.

So the general recommendations are:

  1. If the bug is really small and easy to fix (< 1 day of work), put it into the Minor Fix column in the order of importance
  2. If the bug is complex enough, make sure the bug is reproducible (preferably, ask on IRC) and put it into the Triaged column.