[website-discuss] bugs.os.org

[Richard Lowe]

Shawn Walker wrote:
> On 27/02/07, John Plocher <John.Plocher at sun.com> wrote:
>>
>> >> http://bugs.opensolaris.org/
>>
>> RFE: for the bug form web page:
>>
>> Add a few links on this page for targeted searches (e.g., P1 ON bugs,
>> bugs fixed in last month, bugs filed in last month...) to help newcomers
>> get a feel for what is there and how it is organized.  You know,
>> learning by example and all that...
>>
>> I'm not sure if the bite sized bugs page is generated by this search
>> form, or if it is a custom query, but if it /was/ generated via the
>> search form, the filled out form contents would be a good example as 
>> well.
>>
>>    -John
> 
> To add to John's request, it would be extremely helpful if there was
> an explanation of what the different bug states mean as well as the
> ability to search on more than one state at a time.
> 
> The only state explanation I found was on the oss-bite-size page
> linked from the main bugs page:
> 
> "1-Dispatched     Bug is available to be worked on by community, no
> engineer assigned
> 2-Incomplete     More information needed, not being actively worked: bug
> may be available to be worked on by community
> 3-Accepted     Engineer assigned, may be avaiable for the community to
> work on: contact the Responsible Engineer
> 4-Defer     Not being actively worked: bug may be available to be worked
> on by community"
> 

1-Dispatched      -     Default State
2-Incomplete      -     Not enough information
3-Accepted        -     Yes, that is a problem
4-Defer           -     Accepted, but the fix may not be made soon.
5-Cause Known     -     Bug is root caused
6-Fix Understood  -     Fix is known
7-Fix In Progress -     Fix is in progress
8-Fix Available   -     Fix has been made (either putback, or just prior)
9-Fix Failed      -     Previous fix did not work
10-Fix Delivered  -     Fix available in build
11-Closed         -     Closed

(or something close)

-- Rich