Bug report severity

SomeDude lovelydear at mailmetrash.com
Fri May 11 14:13:07 PDT 2012


On Friday, 11 May 2012 at 08:06:30 UTC, Don Clugston wrote:
> 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.
>

I reduced the criticity because I saw Walter do the same for a 
similar bug with the commment in the lines of: "A wrong error 
message isn't critical"




More information about the Digitalmars-d mailing list