{Spam?} [Fwd: proposal 2]

[Gervase Markham]

Er... why have you sent us this?

Gerv

Josh Soref wrote:
> Date: Fri, 11 Jan 2002 14:57:51 -0500
> From: jesus X <jesusx at who.net>
> To: timeless at bemail.org
> 
>>New proposal with summary at end. I think it still needs a little
>>work...
> 
> 
>>1. Current "Status" and "Resolution" selections insufficent for
>>effective triaging in some circumstances.
>>
>>UNCONFIRMED and NEW are too constrictive and too vague as to the
>>real state of a bug report. There seems to be a need for 
>>intermediate selections based on current triage status.
>>
>>Possible solutions:
>>
>>New potential statuses.
>>CANREPRO - for reproduceable bugs (is this really necessary? dosen't
>>NEW handle this?)
>>NOREPRO - for a failure to reproduce problem
>>NEEDREPRO - alternative to NOREPRO
>>NEEDINFO - for bugs where the info provided by the reporter is
>>insufficient, needs testcase, etc.
>>NEW may need renamed, as it is unclear as to meaning "this is a
>>valid bug" or "this bug was filed by a known-good source, but 
>>may/maynot be a valid bug".
>>Depricate UNCONFIRMED and replace with 2 new states, UNTRIAGED and
>>TRIAGED.
>>
>>--------
>>2. ASSIGNED seems only semi-useful at best, to some. Others see it
>>as very useful.
>>
>>Possible Solutions:
>>More fine grained descriptors. Specific rules about setting a bug
>>ASSIGNED.
>>Renaming ASSIGNED to ACCEPTED (this seems to have some healthy
>>support)
>>Create UNASSIGNED state for valid bugs with little chance to be
>>fixed in the near/not-so-near future.
>>
>>--------
>>3. LATER may need to become depricated and replaced by the 
>>UNASSIGNED state.
>>
>>
>>---------
>>Proposal:
>>---------
>>
>>Depricate or remove the following statuses:
>>  UNCONFIRMED, ASSIGNED, REMIND, LATER
>>
>>Add the following statuses:
>>  UNTRIAGED, TRIAGED, ACCEPTED, UNASSIGNED
>>
>>and add the following Resolutions for TRIAGED bugs:
>>  NEEDREPRO, NEEDINFO
>>
>>UNTRIAGED will replace UNCONFIRMED
>>
>>TRIAGED will have Resolution set to NEEDREPRO, NEEDINFO
>>
>>ACCEPTED will replace ASSIGNED when the bug is actually being
>>actively worked on.
>>
>>UNASSIGNED will be for bugs that are valid, but will not be worked
>>on for the forseeable future.
>>
>>
>>Process:
>>
>>1. Newly filed reports will start out as UNTRIAGED
>>
>>2. Triagers will then change the bug to TRIAGED and either NEEDINFO
>>or NEDREPRO if they cannot reproduce the bug or need more info from
>>the reporter or other triagers, or an UNTRIAGED bug can be changed
>>directly to NEW if they can reproduce it and it does not need info.
>>
>>3. NEW bugs can then either be ACCEPTED by an engineer, or be
>>UNASSIGNED showing it is "up for grabs" and not being worked on at
>>all.
>>
>>
>>Summary: The total possible STATUSes will then be:
>>UNTRIAGED, TRIAGED, NEW, ACCEPTED, UNASSIGNED, REOPENED, RESOLVED,
>>VERIFIED, and CLOSED
>>
>>RESOLUTIONs would be:
>>NEEDREPRO, NEEDINFO, FIXED, WONTFIX, DUPLICATE, WORKSFORME
> 
> 
> ------------------------------------------------------------
> Free, BeOS-friendly email accounts: http://BeMail.org/
> BeOS News and Community: http://www.BeGroovy.com/
> 
> 
> ---------------------------------------------------------------------
> Express yourself with a super cool email address from BigMailBox.com.
> Hundreds of choices. It's free!
> http://www.bigmailbox.com
> ---------------------------------------------------------------------
> ----
> To view or change your list settings, click here:
> <http://bugzilla.org/cgi-bin/mj_wwwusr?user=gerv@mozilla.org>