Re: [bugzilla] replace generic severity descriptions with wine specific ones

[James Hawkins]

On 9/11/07, Lei Zhang <thestig(a)google.com> wrote:
> Hi,
>
> This is for bug 9110. Hopefully bug reporters will stop marking their
> bugs as critical and then get upset when we set it to normal.

<th>Blocker</th>

-    <td>Blocks development and/or testing work</td>
+    <td>When Wine won't start at all for any application, and there's no work
+    around</td>

I think you've made this too specific, especially for Blocker.  For
example, in the new description you've left out compile errors, which
is a big part of what blocker represents.  The original description is
fine for blocker.

     <th>Major</th>

-    <td>major loss of function</td>
+    <td>For a problem that is affecting most applications you run in Wine</td>
+  </tr>

Why not something like,

major loss of functionality for a wide range of applications

instead of totally rewriting the definition.

-- 
James Hawkins

[bugzilla] replace generic severity descriptions with wine specific ones

[Lei Zhang]

On 9/11/07, James Hawkins <truiken(a)gmail.com> wrote:
> On 9/11/07, Lei Zhang <thestig(a)google.com> wrote:
> > Hi,
> >
> > This is for bug 9110. Hopefully bug reporters will stop marking their
> > bugs as critical and then get upset when we set it to normal.
>
> <th>Blocker</th>
>
> -    <td>Blocks development and/or testing work</td>
> +    <td>When Wine won't start at all for any application, and there's no work
> +    around</td>
>
> I think you've made this too specific, especially for Blocker.  For
> example, in the new description you've left out compile errors, which
> is a big part of what blocker represents.  The original description is
> fine for blocker.
>
> <th>Major</th>
>
> -    <td>major loss of function</td>
> +    <td>For a problem that is affecting most applications you run in Wine</td>
> +  </tr>
>
> Why not something like,
>
> major loss of functionality for a wide range of applications
>
> instead of totally rewriting the definition.
>
> --
> James Hawkins

For the most part, I just copy and pasted from the bit at the bottom
of http://wiki.winehq.org/Bugs.

I'll wait for more feedback and then send another patch.

[bugzilla] replace generic severity descriptions with wine specific ones

[Juan Lang]

> I'll wait for more feedback and then send another patch.

If you assume users read the descriptions before choosing a severity,
I think you assume a lot.  I suspect most users choose from the list
of words, assigning their own meaning to them.  So of course, every
bug becomes a "blocker," because hey, it's blocking me getting my work
done.  Modding bugs down, and telling users to vote if they really
care about a bug, is just part of triage.

--Juan

[bugzilla] replace generic severity descriptions with wine specific ones

[Lei Zhang]

On 9/11/07, Juan Lang <juan.lang(a)gmail.com> wrote:
> > I'll wait for more feedback and then send another patch.
>
> If you assume users read the descriptions before choosing a severity,
> I think you assume a lot.  I suspect most users choose from the list
> of words, assigning their own meaning to them.  So of course, every
> bug becomes a "blocker," because hey, it's blocking me getting my work
> done.  Modding bugs down, and telling users to vote if they really
> care about a bug, is just part of triage.
>
> --Juan

Some users do read the severity, and they currently see:

Critical - crashes, loss of data, severe memory leak

so just about anytime Wine crashes, they mark their bugs critical.
When we mod the bug down, they get upset and occasionally sparks fly.