Minnow Bug Triage: Difference between revisions

From Yocto Project
Jump to navigationJump to search
No edit summary
No edit summary
Line 32: Line 32:
   |total=summary
   |total=summary
}}
}}
== MB Open Bugs ==
== MinnowBoard v1 Open Bugs ==
{{#bugzilla:
{{#bugzilla:
   |status=!(RESOLVED,VERIFIED,CLOSED)
   |status=!(RESOLVED,VERIFIED,CLOSED)
Line 42: Line 42:
   |total=summary
   |total=summary
}}
}}
== MBX Open Bugs ==
== MinnowBoard-MAX Open Bugs ==
{{#bugzilla:
{{#bugzilla:
   |status=!(RESOLVED,VERIFIED,CLOSED)
   |status=!(RESOLVED,VERIFIED,CLOSED)

Revision as of 18:35, 24 April 2014

Goal

The output of the bug triage meeting should be that all bugs have an owner, a target milestone, and a priority.

Prior to the meeting, each Product Owner should review their Weekly New and High Bugs and be ready with any opens. An example open would be a bug that may need to change Products.

Agenda

  • Opens
    • Collect opens
    • Discuss opens
  • Review Queries
    • State number and owner
    • Owner makes any modifications
    • Assign owner, target milestone, and priority.


Bug Criteria

  • Priority-Severity
    • High-Critical: Two Week
    • High: Milestone
    • Medium: Nice to have for milestone, must have for release

MinnowBoard Bug Triage Searches

Non-Prioritized Bugs

IDSummarySeverityPMilestoneAssigneeStatusWhiteboardE
 0       

MinnowBoard v1 Open Bugs

IDSummarySeverityPMilestoneAssigneeStatusWhiteboardE
 0       

MinnowBoard-MAX Open Bugs

IDSummarySeverityPMilestoneAssigneeStatusWhiteboardE
 0       
Retrieved from "https://wiki.yoctoproject.org/wiki/index.php?title=Minnow_Bug_Triage&oldid=12637"