Bugzilla - an experiment in trackability

Sean Kelly sean at f4.ca
Sun Mar 5 21:39:36 PST 2006


Brad Roberts wrote:
> On Sun, 5 Mar 2006, Walter Bright wrote:
> 
>> 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
> 
> I'll add these to the page you see when you click on the Priority link 
> when entering a bug.  I tend to think of priority as something that you as 
> the author should be setting.

Same here.  But it's helpful if the submitter can make a reasonable 
guess at categorizing things--I know that I tend to push off bug reports 
with blank priority info and the like until I find time to review 
them... and it's rare that I find that time.  A perfect design may be 
more workflow-oriented, so the recipient could have an inbox of sorts 
where new bugs appear.  Though perhaps there's an easy way to manage 
this with reports?  I'll have to play with Bugzilla a bit more and see.

>> 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
> 
> I tend to think of severity as something the submitter sets, though it can 
> be adjusted certainly.
> 
> IMHO, Severity should be tempered by the nature of the bug.  If it's a 
> crash of the compiler on invalid code that is less severe than a crash on 
> valid code.

Aye.  I was mostly trying to make sure that the existing values were 
meaningful to the recipient.  No reason to use the defaults if an 
alternate definition would be more fitting.

> Some of your descriptions above touch on another area of classification 
> that fits into what bugzilla calls keywords. I've copied the same keywords 
> that the gcc crew use.  Click on the keywords link when submitting a bug 
> to see the list.

Thanks.  I'll give it a look.


Sean



More information about the Digitalmars-d-bugs mailing list