Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 18 Mar 2002 16:29:01 -0800
From:      Luigi Rizzo <rizzo@icir.org>
To:        Dag-Erling Smorgrav <des@ofug.org>
Cc:        bugbusters@FreeBSD.org
Subject:   Re: PR state revision
Message-ID:  <20020318162901.C27352@iguana.icir.org>
In-Reply-To: <xzppu21jtq0.fsf@flood.ping.uio.no>
References:  <xzppu21jtq0.fsf@flood.ping.uio.no>

next in thread | previous in thread | raw e-mail | index | archive | help

the "suspended" by itself makes little sense, given that
nobody will deliberately put a PR in suspended state:
if anything, they will be moved to "closed" state.

I'd rather suggest to just put some code in the generation of
the list of PR's that flags entries whose status has not been
updated for a long time as "stalled" (and maybe showing
them in a different color on the web interface) so people
can be hinted on which entry to close.

	cheers
	luigi

On Tue, Mar 19, 2002 at 01:18:15AM +0100, Dag-Erling Smorgrav wrote:
> In light of the controversy and confusion that reign over the precise
> meaning of the "feedback" state, I would like to suggest the following
> revision of the Gnats states:
> 
>   open          Default state for a new problem report.
> 
>   analyzed      The problem is understood and a solution is being sought.
> 
>   suspended     Work on this PR has been suspended due to lack of
>                 information or resources.
> 
>   feedback      Further work requires additional information from the
>                 originator or the community - possibly confirmation of
>                 the effectiveness of a proposed solution.
> 
>   patched       Patch has been committed, but some issues (MFC and / or
>                 confirmation from originator) are still open.
> 
>   closed        PR has been resolved or abandoned.
> 
> The most significant change is the addition of the "patched" state,
> and the ensuing disambiguation of the "feedback" state.  I would also
> like to encourage the use of the "analyzed" state where appropriate.
> 
> Adding the "patched" state will require modifying the web search form
> and script, and doing a sweep to move "feedback" PRs to "patched"
> where appropriate.
> 
> I will also create and publish a state diagram documenting the
> different states and the recommended transitions from one to the
> other.
> 
> DES
> -- 
> Dag-Erling Smorgrav - des@ofug.org

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugbusters" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020318162901.C27352>