58124 - Please add a severity level of "non-conformant"

Status: RESOLVED WONTFIX

(bugzilla.mozilla.org :: General, enhancement, P3)

Description

[David Flanagan]

I think it would be useful to define a new severity level for bugs
that have to do with compliance to open standards.  For example, I've
been finding problems with the compliance of the javascript engine to
the EcmaScript specification.  Most of the bugs I've found aren't 
terribly severe in day-to-day practice, but because its a standards compliance
issue, I think these bugs should have a high priority.

I propose that the new severity level be called "non-conformant", and that
it appear above "normal" but below "major" in the buzilla menu.

Comment 1

[Brendan Eich [:brendan]]

My 2 cents: severity is not priority, and adding more severity levels (you 
missed the big fight to add "blocker" ;-) just makes for more confusion and 
mis-classified bugs.  I think many of these bugs are low severity on the one 
scale all bugs try to fit on: from crasher/data-loss critical (ok, blocker) to 
trivial, and on beyond Zebra to enhancement.

Rather than split severity hairs, we should (a) prioritize these bugs highly; 
(b) use keywords or status whiteboard pseudo-keywords (those wannabe-keywords 
help us decide when to add a new keyword) to indicate standards problems.  For 
the bugs David has been reporting (which I missed for too long because they were 
unconfirmed, or cuz the JS group gets enough of me even these days!), I have 
used the js1.5 keyword supported at bugzilla.mozilla.org.

/be

Comment 2

[Matthew Tuck [:CodeMachine]]

Dawn, mozilla.org issue.

Comment 3

[Gervase Markham [:gerv]]

We've managed quite well without this up to now :-)

Gerv