Bug System Pilot Dev Workflow: DRAFT Accepted/Understood

[John Pampuch]

Yes.  Somehow I had gotten the impression that we had collapsed Open and 
Evaluated into a single state.

-John

On 1/17/12 1:12 PM, Iris Clark wrote:
> Hi, John.
>
>> So I'll bite.  Can we consider a 'triaged' state, and an 'evaluated'
>> state?  Or perhaps a sub-state to distinguish the two?
>>
>> (My apologies to Rich!)
>>
>> -John
> I'm not quite sure what the reference is to Rich is about, but what you've
> requested is effectively what's currently proposed.  Open is effectively
> "triaged".  Are you suggesting that the name be changed?
>
> Thanks,
> Iris
>
> Summary of Current Status Definitions:
>
> New: A bug/feature request enters this status when it is created and should
> not remain in this status for more than 7 days.
>
> Open: Initial triage has determined that the bug/feature request contains
> sufficient information to estimate the basic feasibility of addressing the
> problem and to prioritize the request. At this point, the report is assumed
> to represent a real problem.  If this is a bug, there is no guarantee that
> the problem has been reproduced.
>
> Evaluated:  A developer has performed some investigation to understand the
> nature of the problem.
>
>    Cause Known - A developer has performed sufficient investigation to gain
>    a basic understanding of how this bug/feature request should be addressed.
>    There is no requirement that an actual solution be known at this time.
>
>    Fix Understood - A developer believes that they have a feasible approach
>    to address the problem.  For straight-forward problems, an actual solution
>    may be known.  More complex problems may still need additional study to
>    work out the details.
>
>