Severities and priorities in bugzilla
Wolfgang Bangerth
bangerth@ices.utexas.edu
Tue Jun 3 15:26:00 GMT 2003
We presently have 6 severity and 5 priority classes in bugzilla.
management.html documents them as
Severity -- This field describes the impact of a bug.
Blocker Blocks development and/or testing work
Critical crashes, loss of data, severe memory leak
Major major loss of function
Minor minor loss of function, or other problem where easy
workaround is present
Trivial cosmetic problem like misspelled words or misaligned text
Enhancement Request for enhancement
Priority -- This field describes the importance and order in which a bug
should be fixed. It is utilized by the programmers/engineers
to prioritize their work to be done. The available priorities are:
P1 Most important
P2 More important
P3
P4 Less important
P5 Least important
Apart from the fact that the description of the severities seems not
really taylored to gcc, I think that these are just too many different
states. Daniel, can these states be reduced? How about
Severities
Critical A regression or other important broken functionality
Normal Any bug where gcc generates wrong code or doesn't conform
to some relevant standard, or where diagnostics are
misleading
Minor Small enhancements, minor stuff that does not affect
usability of gcc but would be nice to have
Priorities
P1 Most important. Should be fixed in the next possible
release
P2 Should eventually be fixed, but no timeframe is set
P3 Least important
To me, having Severity, Priority, and Milestone is still a little
confusing. Is there a way to enforce that all P1 priority bugs have a
milestone set?
W.
-------------------------------------------------------------------------
Wolfgang Bangerth email: bangerth@ices.utexas.edu
www: http://www.ices.utexas.edu/~bangerth/
More information about the Gcc
mailing list