3,267
edits
Changes
Jump to navigation
Jump to search
Line 66:
Line 66: + + + + +
→Priority
scale based on subjective questions like 'would we be embarassed to
scale based on subjective questions like 'would we be embarassed to
release the software with this bug.'
release the software with this bug.'
Immediate This bug blocks development or testing work and should be
Immediate This bug blocks development or testing work and should be
fixed ASAP, or is a security issue in a released version of the software.
fixed ASAP, or is a security issue in a released version of the software.
Urgent This bug blocks usability of a large portion of the product, and
Urgent This bug blocks usability of a large portion of the product, and
really should be fixed before the next planned release.
really should be fixed before the next planned release.
High Seriously broken, but not as high impact. Should be fixed before
High Seriously broken, but not as high impact. Should be fixed before
next major release. Frequently includes cosmetic bugs of particularly
next major release. Frequently includes cosmetic bugs of particularly
high visibility, regressions from functionality provided in previous
high visibility, regressions from functionality provided in previous
releases, and more minor bugs that are frequently reported.
releases, and more minor bugs that are frequently reported.
Normal Either a fairly straightforward workaround exists or the
Normal Either a fairly straightforward workaround exists or the
functionality is not very important and/or not frequently used.
functionality is not very important and/or not frequently used.
Low Just not all that important. Rarely used in GNOME.
Low Just not all that important. Rarely used in GNOME.