[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-30 15:56:32
Message-ID: PzXEPwhxPXjKnruC4gr5xeXnY6YVFByWctolB5pgIHfYlpMZS5sMTDBt2Nj9JQextNJnwqoIXgE6JF2PX8nsOOsXW3o10DKt5vbWw8ojIJ0= () crouthamel ! us
[Download RAW message or body]

[Attachment #2 (text/plain)]

I like OPENED as well.

-------- Original Message --------
On Sep 29, 2018, 6:17 PM, Ben Cooksley wrote:

> On Sun, Sep 30, 2018 at 9:44 AM Valorie Zimmerman
> <valorie.zimmerman@gmail.com> wrote:
>>
>> On Fri, Sep 28, 2018 at 1:48 AM Luigi Toscano <luigi.toscano@tiscali.it> wrote:
>>>
>>> Kai Uwe Broulik ha scritto:
>>> > Hi,
>>> >
>>> > > Here is my follow-up change recommendation based on feedback and research:
>>> > >
>>> > > UNCONFIRMED -> REPORTED
>>> > > WONTFIX -> INTENTIONAL
>>> > > INVALID -> NOTABUG
>>> >
>>> > one issue I'm having with "REPORTED" is that it shows up as "REPO" in the list
>>> > and can easily be confused with "REOP" for "REOPENED". Perhaps we need
>>> > something different for Reopened then.
>>>
>>> If we rename also that, we would have two bug names diverging from the other
>>> bug trackers, instead of just one. Moreover I find that there is no much to
>>> discuss on the appropriateness of REOPENED.
>>> I'd rather find an alternative for REPORTED, if this confusion is going to be
>>> an issue.
>>>
>>> --
>>> Luigi
>>
>>
>> OPENED ?
>
> Definitionally reported is definitely the right word to be using, but
> given that conflict/simiilarity between REPO/REOP I think opened is
> probably the best term we can get here.
> None of the synonyms for reported fit that's for sure.
>
>>
>> Valorie
>> --
>> http://about.me/valoriez
>>
>>
>
> Cheers,
> Ben
[Attachment #3 (text/html)]

I like OPENED as well. <br><br><br><br><br><br><br>-------- Original Message \
--------<br>On Sep 29, 2018, 6:17 PM, Ben Cooksley < bcooksley@kde.org> \
wrote:<blockquote class="protonmail_quote"><br><p dir="ltr">On Sun, Sep 30, 2018 at \
9:44 AM Valorie Zimmerman<br> &lt;<a \
href="mailto:valorie.zimmerman@gmail.com">valorie.zimmerman@gmail.com</a>&gt; \
wrote:<br> &gt;<br>
&gt; On Fri, Sep 28, 2018 at 1:48 AM Luigi Toscano &lt;<a \
href="mailto:luigi.toscano@tiscali.it">luigi.toscano@tiscali.it</a>&gt; wrote:<br> \
&gt;&gt;<br> &gt;&gt; Kai Uwe Broulik ha scritto:<br>
&gt;&gt; &gt; Hi,<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; &gt; Here is my follow-up change recommendation based on feedback and \
research:<br> &gt;&gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; UNCONFIRMED -&gt; REPORTED<br>
&gt;&gt; &gt; &gt; WONTFIX -&gt; INTENTIONAL<br>
&gt;&gt; &gt; &gt; INVALID -&gt; NOTABUG<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; one issue I'm having with "REPORTED" is that it shows up as "REPO" in \
the list<br> &gt;&gt; &gt; and can easily be confused with "REOP" for "REOPENED". \
Perhaps we need<br> &gt;&gt; &gt; something different for Reopened then.<br>
&gt;&gt;<br>
&gt;&gt; If we rename also that, we would have two bug names diverging from the \
other<br> &gt;&gt; bug trackers, instead of just one. Moreover I find that there is \
no much to<br> &gt;&gt; discuss on the appropriateness of REOPENED.<br>
&gt;&gt; I'd rather find an alternative for REPORTED, if this confusion is going to \
be<br> &gt;&gt; an issue.<br>
&gt;&gt;<br>
&gt;&gt; --<br>
&gt;&gt; Luigi<br>
&gt;<br>
&gt;<br>
&gt; OPENED ?</p>
<p dir="ltr">Definitionally reported is definitely the right word to be using, \
but<br> given that conflict/simiilarity between REPO/REOP I think opened is<br>
probably the best term we can get here.<br>
None of the synonyms for reported fit that's for sure.</p>
<p dir="ltr">&gt;<br>
&gt; Valorie<br>
&gt; --<br>
&gt; <a href="http://about.me/valoriez">http://about.me/valoriez</a><br>
&gt;<br>
&gt;</p>
<p dir="ltr">Cheers,<br>
Ben<br>
</p>
</div>



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

Configure | About | News | Add a list | Sponsored by KoreLogic