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: Ulrich Mueller <ulm@g.o>
Subject: Re: Bugzilla - New Default Status Workflow
Date: Sun, 6 Mar 2011 14:39:01 +0100
>>>>> On Sun, 6 Mar 2011, Christian Ruppert wrote:

> This will convert the status of all bugs using the following
> system:

>   "NEW" will become "CONFIRMED"

Weird. How can a newly added bug be "CONFIRMED", unless someone has
taken some action to confirm it?

> This change will be immediate. The history of each bug will also be
> changed so that it appears that these statuses were always in
> existence.

So all bugs currently marked as "NEW" or "REOPENED" will change their
status to "CONFIRMED"? That doesn't look right to me. Would that
status change be visible in the bug's history?

> So, do we want the new workflow or do we want to keep the old?

If the new workflow implies such status changes on existing bugs, then
keep the old one please.

Ulrich


Replies:
Re: Bugzilla - New Default Status Workflow
-- Nirbheek Chauhan
References:
Bugzilla - New Default Status Workflow
-- Christian Ruppert
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Re: Re: Bugzilla - New Default Status Workflow
Next by thread:
Re: Bugzilla - New Default Status Workflow
Previous by date:
Re: gtk 3 preparation work
Next by date:
Re: Bugzilla - New Default Status Workflow


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.