Changes

BugSquad/Status Fields (view source)

Revision as of 11:39, 2 January 2009

38 bytes added , 11:39, 2 January 2009

→‎Priority

Line 59: Line 59:

'''Enhancement''' Request for a new feature or functionality.

−

== Priority ==

+

== Priority (GNOME) ==

This field describes the importance and order in which a bug should be

fixed. This field is utilized by hackers to prioritize their work to be

−

done. While each term has a description, it it important to note that

+

done. While each term has a description, it is important to note that

priority is highly subjective, and bugs can move up or down the priority

scale based on subjective questions like 'would we be embarassed to

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.

−

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.

−

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

high visibility, regressions from functionality provided in previous

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.

−

Low Just not all that important. Rarely used in Sugar.

+

'''Low''' Just not all that important. Rarely used in Sugar.

== Target Milestone ==

Erikos

3,267

edits