Any guideline about severity of bugs?
Dukc
ajieskola at gmail.com
Mon Jul 18 11:28:52 UTC 2022
Apart from regressions being considered the worst bugs, I don't
know of any guideline on evaluating a severity of a bug I'm
reporting. I feel this is a problem. Because everyone has a
different perception of what consitutes, for example, a "major"
bug, this means that two bug reports about the same issue may
differ by multiple severity levels.
For example, my personal rule has long been "if the compiler
crashes from using a vanilla, or soon-vanilla (DIP1000) language
feature, it's automatically critical". But some report those
issues [as
"normal"](https://issues.dlang.org/show_bug.cgi?id=19932). I
don't know which is right, and I don't think anyone else knows
either.
This means that those who are bold with assigning severity levels
get more attenton than those who downplay their bugs severity for
fear of dramamongering accusations, or something. Also it's hard
to override the severity of bug reports of others even when I
feel it's wrong, when there is no guideline to say which
interpretation is right.
Are there any guidelines that I'm not aware of? If not, I think
they should be laid down. It does not need to be anything
complex, just several rules and examples to get us started.
More information about the Digitalmars-d
mailing list