[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-community
Subject: Re: Improving Bugzilla Status Names
From: David Jarvie <djarvie () kde ! org>
Date: 2018-09-30 16:39:04
Message-ID: 401517CC-150E-4400-922A-CFB9CDA0D3AA () kde ! org
[Download RAW message or body]
On 28 September 2018 09:48:42 BST, 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
I think that REPORTED is an ideal term for a newly opened bug. Is there really a \
problem with the abbreviations REPO and REOP? Surely people will quickly get used to \
making the distinction, if they make a mistake at all. In any case, as soon as the \
bug report is accessed, it will be clear what its status is. Please keep REPORTED and \
REOPENED as they are.
--
David Jarvie
KAlarm author, KDE developer
http://www.astrojar.org.uk/kalarm
[Attachment #3 (text/html)]
<html><head></head><body><br><br><div class="gmail_quote">On 28 September 2018 \
09:48:42 BST, Luigi Toscano <luigi.toscano@tiscali.it> wrote:<blockquote \
class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, \
204, 204); padding-left: 1ex;"> <pre class="k9mail">Kai Uwe Broulik ha \
scritto:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; \
border-left: 1px solid #729fcf; padding-left: 1ex;">Hi,<br><br><blockquote \
class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #ad7fa8; \
padding-left: 1ex;"> Here is my follow-up change recommendation based on feedback and \
research:<br><br> UNCONFIRMED -> REPORTED<br> WONTFIX -> INTENTIONAL<br> \
INVALID -> NOTABUG<br></blockquote><br>one issue I'm having with "REPORTED" is \
that it shows up as "REPO" in the list <br>and can easily be confused with "REOP" for \
"REOPENED". Perhaps we need <br>something different for Reopened \
then.<br></blockquote><br>If we rename also that, we would have two bug names \
diverging from the other <br>bug trackers, instead of just one. Moreover I find that \
there is no much to <br>discuss on the appropriateness of REOPENED.<br>I'd rather \
find an alternative for REPORTED, if this confusion is going to be <br>an \
issue.<br></pre></blockquote></div><br>I think that REPORTED is an ideal term for a \
newly opened bug. Is there really a problem with the abbreviations REPO and REOP? \
Surely people will quickly get used to making the distinction, if they make a mistake \
at all. In any case, as soon as the bug report is accessed, it will be clear what its \
status is. Please keep REPORTED and REOPENED as they are.<br><br>--<br>David \
Jarvie<br>KAlarm author, KDE developer<br><a \
href="http://www.astrojar.org.uk/kalarm">http://www.astrojar.org.uk/kalarm</a><br></body></html>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic