1,894
edits
Changes
Jump to navigation
Jump to search
New page: == Alternate system == I think it would be better to work with the existing bugzilla concepts, so here's a proposal. ; UNCONFIRMED : These are bugs reported by regular users (currently d...
== Alternate system ==
I think it would be better to work with the existing bugzilla concepts, so here's a proposal.
; UNCONFIRMED
: These are bugs reported by regular users (currently disabled)
: > '''NEW''' if the bug can be confirmed [bug triager]
: > '''RESOLVED INVALID''' if it's not a bug. [bug triager]
: > '''RESOLVED WORKSFORME''' if it can't be reproduced. [bug triager]
; NEW
: Confirmed bugs. No special action is required, but further testing should be done where needed.
: > '''ASSIGNED''' when appopriate [bug lead]
; ASSIGNED
: Bug assigned to a developer for fixing. Only a limited number of bugs should be assigned at any given time.
: > '''RESOLVED FIXED''' if the bug is fixed [dev]
: > '''RESOLVED WONTFIX''' if the dev refuses to fix it [dev]
: > '''RESOLVED REMIND''' to postpone the bug [dev]
: > '''RESOLVED LATER''' to postpone the bug [dev]
; RESOLVED
: These bugs are "finished" according to the last person to change them.
: > '''VERIFIED''' to confirm the resolution [bug triager]
; VERIFIED
: These bugs have been independently confirmed as "finished".
; CLOSED
: Not used.
Note that since normal users can't report bugs, all added bugs are implicitly confirmed by the person adding them, and start in NEW.
Bug triagers can also change the ''severity'' and ''priority'' fields to help the bug lead make decisions on which bugs to assign.
Priority suggests how fast the bug should be fixed:
* '''P1''' should be fixed in the first coming update
* '''P2''' is high priority
* '''P3''' is the default
* '''P4''' is low priority
* '''P5''' is completely unimportant
''Severity'' indicates how much damage the bug does:
; Blocker
: A new version cannot be released until this bug is fixed.
: This field makes most sense for bugs in test server/client.
; Severe
: Major exploits.
: Widespread crashes.
: Significant number of users unable to play properly.
; Major
: Minor exploits.
: Uncommon crashes.
: Small number of users unable to play properly.
; Normal
: The default
; Minor
: Bugs with easy workarounds.
: Unessential features.
; Trivial
: Spelling errors, incorrect message text.
: Other cosmetic errors.
; Enhancement
: Feature request. Bugs with this severity should be closed.
I think it would be better to work with the existing bugzilla concepts, so here's a proposal.
; UNCONFIRMED
: These are bugs reported by regular users (currently disabled)
: > '''NEW''' if the bug can be confirmed [bug triager]
: > '''RESOLVED INVALID''' if it's not a bug. [bug triager]
: > '''RESOLVED WORKSFORME''' if it can't be reproduced. [bug triager]
; NEW
: Confirmed bugs. No special action is required, but further testing should be done where needed.
: > '''ASSIGNED''' when appopriate [bug lead]
; ASSIGNED
: Bug assigned to a developer for fixing. Only a limited number of bugs should be assigned at any given time.
: > '''RESOLVED FIXED''' if the bug is fixed [dev]
: > '''RESOLVED WONTFIX''' if the dev refuses to fix it [dev]
: > '''RESOLVED REMIND''' to postpone the bug [dev]
: > '''RESOLVED LATER''' to postpone the bug [dev]
; RESOLVED
: These bugs are "finished" according to the last person to change them.
: > '''VERIFIED''' to confirm the resolution [bug triager]
; VERIFIED
: These bugs have been independently confirmed as "finished".
; CLOSED
: Not used.
Note that since normal users can't report bugs, all added bugs are implicitly confirmed by the person adding them, and start in NEW.
Bug triagers can also change the ''severity'' and ''priority'' fields to help the bug lead make decisions on which bugs to assign.
Priority suggests how fast the bug should be fixed:
* '''P1''' should be fixed in the first coming update
* '''P2''' is high priority
* '''P3''' is the default
* '''P4''' is low priority
* '''P5''' is completely unimportant
''Severity'' indicates how much damage the bug does:
; Blocker
: A new version cannot be released until this bug is fixed.
: This field makes most sense for bugs in test server/client.
; Severe
: Major exploits.
: Widespread crashes.
: Significant number of users unable to play properly.
; Major
: Minor exploits.
: Uncommon crashes.
: Small number of users unable to play properly.
; Normal
: The default
; Minor
: Bugs with easy workarounds.
: Unessential features.
; Trivial
: Spelling errors, incorrect message text.
: Other cosmetic errors.
; Enhancement
: Feature request. Bugs with this severity should be closed.
