[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-community
Subject:    Re: Improving Bugzilla Status Names
From:       Andrew Crouthamel <andrew () crouthamel ! us>
Date:       2018-09-05 8:17:28
Message-ID: iijbq4-bloV0hL87FO_TVKBpeKYrZDpoKaOFnq2D8cBYcWoeigbYKtTRzYUyhdj_O7kpRXyZdV0PpsNpsu-nw49vqpiIjpfK81Co-kXCqzo= () crouthamel ! us
[Download RAW message or body]

[Attachment #2 (text/plain)]

I like REPORTED as well. That leaves timeframe out of the status name. Bugs can stay \
REPORTED but never CONFIRMED, and that all makes sense.

Based on David's feedback, this would work for his needs I believe.

As for WONTFIX vs. ASDESIGNED, Ilmari, do you have any suggestions for alternatives? \
I know that isn't perfect, but was the best we could come up with so far.

Andrew Crouthamel

-------- Original Message --------
On Sep 5, 2018, 12:03 AM, Nate Graham wrote:

> On 09/04/2018 10:01 PM, Christoph Feck wrote:
> > I still oppose to name a status NEW (again). It only attracts "how is
> > this NEW? this is already [random timespan here] OLD!" comments.
> > There will always be products/components that have no active maintainer
> > to look for bugs in a limited timeframe.
> > 
> > My suggestions are OPEN, REPORTED, or UNRESOLVED.
> 
> I could get behind OPEN or REPORTED.
> 
> Nate


[Attachment #3 (text/html)]

I like REPORTED as well. That leaves timeframe out of the status name. Bugs can stay \
REPORTED but never CONFIRMED, and that all makes sense.<br><br>Based on David's \
feedback, this would work for his needs I believe. <br><br>As for WONTFIX vs. \
ASDESIGNED, Ilmari, do you have any suggestions for alternatives? I know that isn't \
perfect, but was the best we could come up with so far. <br><br>Andrew Crouthamel \
<br><br><br><br>-------- Original Message --------<br>On Sep 5, 2018, 12:03 AM, Nate \
Graham < nate@kde.org> wrote:<blockquote class="protonmail_quote"><br><p \
dir="ltr"></p> <p dir="ltr">On 09/04/2018 10:01 PM, Christoph Feck wrote:<br>
&gt; I still oppose to name a status NEW (again). It only attracts "how is <br>
&gt; this NEW? this is already [random timespan here] OLD!" comments.<br>
&gt; There will always be products/components that have no active maintainer <br>
&gt; to look for bugs in a limited timeframe.<br>
&gt; <br>
&gt; My suggestions are OPEN, REPORTED, or UNRESOLVED.</p>
<p dir="ltr">I could get behind OPEN or REPORTED.</p>
<p dir="ltr">Nate</p>
</div>



[prev in list] [next in list] [prev in thread] [next in thread]