Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-dev
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-dev@g.o
From: Ryan Hill <dirtyepic@g.o>
Subject: Re: Bugzilla - New Default Status Workflow
Date: Thu, 10 Mar 2011 22:35:55 -0600
On Fri, 11 Mar 2011 04:52:19 +0100
Jeroen Roovers <jer@g.o> wrote:

> On Thu, 10 Mar 2011 21:06:54 +0100
> Amadeusz Żołnowski <aidecoe@g.o> wrote:
> 
> > > Status = NEW && Assignee = bug-wranglers -> Status = UNCONFIRMED
> > > Status = NEW && Assignee = [maintainer] -> Status = CONFIRMED
> > 
> > Who confirms the bug?  I would expect that CONFIRMED is set by the
> > package maintainer and the one who assigns bugs leaves the status.
> 
> I was referring to existing bug reports, not new ones. New ones should
> come in as UNCONFIRMED and would be changed to CONFIRMED when assigned
> - bug wrangling does have this element of validation, you know.
> Apparently when maintainers accept the bug, it changes to IN PROGRESS,
> and when [s]he doesn't it should be resolved as invalid or duplicate
> or whatever, but heck, maybe the flow chart should speak for itself.

Bug wranglers should only mark bugs CONFIRMED if they can personally
reproduce them.  If no one has produced the bug other than the original
poster then that's the very definition of UNCONFIRMED.

Or maybe you're thinking CONFIRMED as in "I confirm this is a bug report and
not a lunch order"?


-- 
fonts, gcc-porting,                  it makes no sense how it makes no sense
toolchain, wxwidgets                           but i'll take it free anytime
@ gentoo.org                EFFD 380E 047A 4B51 D2BD C64F 8AA8 8346 F9A4 0662
Attachment:
signature.asc (PGP signature)
References:
Bugzilla - New Default Status Workflow
-- Christian Ruppert
Re: Bugzilla - New Default Status Workflow
-- Brian Harring
Re: Bugzilla - New Default Status Workflow
-- Paweł Hajdan, Jr.
Re: Bugzilla - New Default Status Workflow
-- Brian Harring
Re: Bugzilla - New Default Status Workflow
-- Paweł Hajdan, Jr.
Re: Bugzilla - New Default Status Workflow
-- Markos Chandras
Re: Bugzilla - New Default Status Workflow
-- Mike Gilbert
Re: Bugzilla - New Default Status Workflow
-- Jeroen Roovers
Re: Bugzilla - New Default Status Workflow
-- Jeroen Roovers
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Re: Bugzilla - New Default Status Workflow
Next by thread:
Re: Bugzilla - New Default Status Workflow
Previous by date:
Re: Bugzilla - New Default Status Workflow
Next by date:
Re: Quantity of open bugs


Updated Jun 29, 2012

Summary: Archive of the gentoo-dev mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.