From: "\"Paweł Hajdan, Jr.\"" <phajdan.jr@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Does anyone use the VERIFIED status in bugzilla?
Date: Fri, 14 May 2010 16:08:27 +0200 [thread overview]
Message-ID: <4BED595B.8050009@gentoo.org> (raw)
In-Reply-To: <4BED5613.4020603@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1069 bytes --]
On 5/14/10 3:54 PM, Matti Bickel wrote:
>>From my work on b.g.o: I use a simplified version of this, shown at:
> http://dev.gentoo.org/~mabi/gentooBzLifecycle.png
Yeah, I think the linked diagram really reflects the reality, much
better than the "official" one. I'm in favor of removing the "Verified"
resolution to clean things up.
I haven't seen a project where the "Verified" status would be useful.
Generally the reporters re-open their bugs if they are not satisfied.
Also, for many classes of bugs verification gives absolutely no
benefits, e.g. keywording, stabilization, etc.
If we want to keep "Verified", then in my opinion some group should be
created to verify bugs consistently. If it's just one user doing it, I
see no benefits, and only background noise.
Note: maybe that user would like to help in the bugzilla in a way we'd
all agree to be useful. For example wrangling bugs (assigning to right
owners, getting more info, etc). Please make sure not to discourage him
from contributing more by too harsh comments.
Paweł
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2010-05-14 14:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-14 12:45 [gentoo-dev] Does anyone use the VERIFIED status in bugzilla? Jorge Manuel B. S. Vicetto
2010-05-14 13:28 ` Fabian Groffen
2010-05-14 13:34 ` Samuli Suominen
2010-05-14 13:54 ` Matti Bickel
2010-05-14 14:08 ` "Paweł Hajdan, Jr." [this message]
2010-05-14 14:10 ` Richard Freeman
2010-05-14 16:01 ` Joshua Saddler
2010-05-15 19:39 ` Rémi Cardona
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4BED595B.8050009@gentoo.org \
--to=phajdan.jr@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox