[Bug 6506] Poor bug severity classification practices

[Wine Bugs]

http://bugs.winehq.org/show_bug.cgi?id=6506

[e-mail] changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|critical                    |normal
             Status|CLOSED                      |UNCONFIRMED
          Component|wine-binary                 |misc-bugs
         OS/Version|Linux                       |All
            Product|Wine                        |WineHQ Bugzilla
         Resolution|INVALID                     |
            Summary|Socket/file handle leak     |Poor bug severity
                   |                            |classification practices

------- Additional Comments From [e-mail]  2006-23-10 14:58 -------
Reopening. This is a Wine Bugzilla QA issue and it remains unaddressed: Why will
you not mark as "critical" a bug with multiple confirmations that is clearly
"critical" by Wine Bugzilla standards?

Since last March several users have been requesting in bug 3063 for that bug to
be reclassified as "critical", but that request has been ignored. Because of
this it would seem that commenting in the bug itself isn't the proper (or
adequate) channel for resolving such a matter, and that is why I filed this new
bug. If you still believe this to be an abuse of Bugzilla, then please clarify
what should be done to resolve situations where a bug is wrongly classified, and
explain why the Severity field is being treated inconsistently in the case of
bug 3063.