Bugzilla - an experiment in trackability

[Walter Bright]

"Sean Kelly" <sean at f4.ca> wrote in message 
news:dufhan$uj9$1 at digitaldaemon.com...
> It would be nice to establish some submission guidelines, particularly on 
> how to set priority and severity.

Priority:

P1: so bad that an update needs to happen immediately; i.e. it makes D 
unusable
P2: fold into next update; things that break existing code go here
P3: should get around to fixing sooner or later
P4: defer until next major version
P5: informational; nobody really cares

Severity:

blocker - prevents use of a major component of D, such as phobos
critical - silent generation of bad code
major - produces compiler crash or generation of internal error messages
normal - garden variety bugs
minor - easy workaround
trivial - only of interest to compiler validation test suites
enhancement - change to documented behavior

> Would Walter prefer test cases entered in the description or attached as 
> files?  I've done the former for old bugs, but it would be useful to know 
> how to format future reports.

If the size is reasonably small, they should be in the description.