gmane.comp.telephony.pbx.asterisk.devel

Joshua Colp | 11 Aug 16:45

Re: [policy] Bug Tracker Workflow Discussion

----- "Leif Madsen" <leif.madsen <at> asteriskdocs.org> wrote:

> ~~~~~~~~~~~~~~~~~~~~
> 
> BUG TRACKER WORKFLOW
> 
> The workflow in the bug tracker should be handled in the following
> way:
> 
> 1) A bug is reported and is automatically placed in the 'new' status.

Don't forget this is not always true presently. Some individuals are setup to automatically be assigned
when issues are filed against certain categories. An example would be Tilghman who gets automatic
assignment of func_odbc issues. If this remains then the issue may not show up on the radar of those who are
looking for new issues to check categorization on/initial triage. We'll either have to stop automatic
assignment or remember to do it.

> 2) The Bug Marshall team should go through bugs in the 'new' status to
> 
> determine whether the report is valid (not a duplicate, hasn't already
> 
> been fixed, not a Digium tech support issue, etc.).  Invalid reports 
> should be set to 'closed' with the appropriate resolution.  Categories
> 
> and descriptions should be corrected at this point.[Note1]

Sounds good. Always great to have the right category and a good description.

> 3) The next step is to determine whether the report is about a bug or
> a

(Continue reading)

headers

Leif Madsen | 11 Aug 19:50

Re: [policy] Bug Tracker Workflow Discussion

Joshua Colp wrote:
> ----- "Leif Madsen" <leif.madsen <at> asteriskdocs.org> wrote:
> 
>> ~~~~~~~~~~~~~~~~~~~~
>>
>> BUG TRACKER WORKFLOW
>>
>> The workflow in the bug tracker should be handled in the following
>> way:
>>
>> 1) A bug is reported and is automatically placed in the 'new' status.
> 
> Don't forget this is not always true presently. Some individuals are setup to automatically be assigned
when issues are filed against certain categories. An example would be Tilghman who gets automatic
assignment of func_odbc issues. If this remains then the issue may not show up on the radar of those who are
looking for new issues to check categorization on/initial triage. We'll either have to stop automatic
assignment or remember to do it.

Hrmmm, that makes sense. Maybe I'll add a note about that, but if they 
are automatically assigned, I see no reason to have to do it manually. 
The person who is automatically assigned the issue should know enough 
how to move the bug through the workflow.

>> 3) The next step is to determine whether the report is about a bug or
>> a 
>> submission of a new feature:
>>
>>       a) BUG: A bug should be moved into the status 'acknowledged'.
>> The 
>> bug may also be assigned to a developer for the creation of the

(Continue reading)