public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Richard Freeman <rich0@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 10:10:29 -0400	[thread overview]
Message-ID: <4BED59D5.6060109@gentoo.org> (raw)
In-Reply-To: <4BED517A.4090709@gentoo.org>

On 05/14/2010 09:34 AM, Samuli Suominen wrote:
> I'd like to see the whole thing go away. It's this one user I've pretty
> much ever seen using it. And he's using it to change "RESOLVED" status
> to "VERIFIED" on e.g. removal bugs, stabilization bugs, keywording bugs...

I think that VERIFIED could have a place in a serious quality management 
system that closes the loop on every change.  If we had a test branch 
and a release branch the VERIFIED might be the glue that moves patches 
from one to the other.

However, we don't have anything like this in place right now, and so 
this is really just spam.  Having the extra state does no good without 
all the processes that go with it.

Would Gentoo have a higher level of quality if we did some CMM-5 
practices like these?  Absolutely!  Would it struggle to keep up with 
Debian Stable?  Absolutely!   I don't think we really have the resources 
to pull off something like this.  As it is we struggle with the current 
~arch/arch system.

I'd get rid of it...



  parent reply	other threads:[~2010-05-14 14:10 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."
2010-05-14 14:10   ` Richard Freeman [this message]
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=4BED59D5.6060109@gentoo.org \
    --to=rich0@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