Bug report severity

[Don Clugston]

On 11/05/12 00:28, Mehrdad wrote:
> On Thursday, 10 May 2012 at 22:23:15 UTC, Stewart Gordon wrote:
>> On 10/05/2012 23:12, Mehrdad wrote:
>>> How do you decide if something is 'critical', 'major', 'blocker', or
>>> just 'normal'? Is
>>> there a rule of thumb I could use?
>>
>> http://d.puremagic.com/issues/page.cgi?id=fields.html#bug_severity
>>
>> Stewart.
>
> Hmmm... thanks for the link.
>
> I'm having trouble understanding how to apply them, though.
>
> For example, why are these bugs "critical"?
> http://d.puremagic.com/issues/show_bug.cgi?id=5314

Because an error message with no clue of where it happened, is pretty 
much the same as a segfault. It's far more important than any other 
'diagnostic' bug.

> http://d.puremagic.com/issues/show_bug.cgi?id=3445

Because this affects the documentation for all of Phobos. It has a huge 
impact. It's far more important than any other 'ddoc' bug.

> Are things like "wrong error message" or "wrong documentation"
> considered to be on par with ICEs?

No, only error messages without line number.

> Like, I see an ICE like
> http://d.puremagic.com/issues/show_bug.cgi?id=6774
>
> and I wonder why it's not "blocker" or at least "critical"...

They have the 'ice' keyword which performs the same job.

The severities are most useful for distinguishing when a bug has a very 
different importance to others in the same category.