1 #summary Classification of bugs

     2 

     3 We classiy [https://issues.hedgewars.org/describecomponents.cgi?product=Hedgewars bugs in Hedgewars] by 1) severity and 2) priority.

     4 

     5 Severity tells us how much a bug “breaks Hedgewars”.

     6 

     7 Priority is less important and is just a rough estimate how “important” a bug is within a severity class.

     8 

     9 == Severity ==

    10 Severity tells us how much “damage” this bug deals to Hedgewars. The higher the severity of a bug, the more it “breaks” Hedgewars. High-serverity bugs are usually also more important and those should usually get more attention as well.

    11 

    12 === Summary ===

    13 Summary of bug severities:

    14 

    15  * *Blocker*: Most serious bugs. Must be fixed before next release

    16  * *Critical*: Crashes and and similar show-stoppers

    17  * *Major*: A key feature is broken or game quality is lowered significantly

    18  * *Normal*: Less-important feature is kinda broken

    19  * *Minor*: Somethng is slightly irritating or weird

    20  * *Trivial*: Nitpicking

    21  * *Enhancement*: Feature request (not a bug)

    22 

    23 === Blocker ===

    24 Anything which must be fixed before release. Including:

    25 

    26  * Hedgewars does not work at all on one of the main platforms

    27  * Very obvious crashes

    28  * Half-finished feature (either finish it or drop it before release)

    29  * Important build script broken

    30  * Regression (a bug that did not exist in the previous release)

    31 

    32 === Crticial ===

    33 Any crash, network desynchronization bugs or other bugs that stop the game completely. The most serious bugs of this kind should be classified as blocker.

    34 

    35 === Major ===

    36 A major feature of Hedgewars is obviously broken which lowers the quality notably. The game is still playable as a whole. Including:

    37 

    38  * Any game-breaking bug. A key aspect of gameplay is broken in an important way, including weapon behaviour. Seriously affects balancing

    39  * A weapon or utility is seriously broken, no real workaround

    40  * Sound does not work

    41  * Obvious and/or annoyingly broken graphics

    42  * Broken video recorder

    43  * Very annoying usability failure

    44 

    45 === Normal ===

    46 A less-important feature of Hedgewars is kinda broken. Like:

    47 

    48  * A gameplay aspect is a bit broken. It might affect gameplay negatively a bit. Workaround might be available

    49  * A projectile/object/gear behaves incorrectly, but not in a game-breaking way

    50  * Mildly annoying usability failure

    51  * Notable but unimportant graphical glitch

    52  * Important broken translation

    53 

    54 === Minor ===

    55 Bugs with low impact, including:

    56 

    57  * Gameplay aspect is a bit weird/confusing, but not broken

    58  * Computer player does something stupid

    59  * Slightly irritating or low quality graphics and sounds

    60  * Minor graphical glitch

    61  * Subtly broken translations

    62  * Code quality complaints

    63 

    64 === Trivial ===

    65 Anything less important than minor. For nitpickers and perfectionists. Rarely used. For bugs like:

    66 

    67  * “Oh no! This image is off by 2 pixels!”

    68  * Very slightly weird GUI

    69  * Typos

    70 

    71 === Enhancement ===

    72 For any feature requests. 

    73 

    74 == Priority ==

    75 Priority of bugs is a rough estimate of how common or important the bug is estimated to be within the assigned severity class. Priority is a less important classification than severity and just a rough guideline. Generally the more likely it is to experience the bug, the higher its priority. Priority is optional does not need to be specified, it can always be added later.

    76 

    77 For enhancements, the priority marks the “desirability” of the feature request. High-priority feature requests should generally be implemented before the lower priority ones.