Minnow Bug Triage: Difference between revisions
From Yocto Project
Jump to navigationJump to search
No edit summary |
No edit summary |
||
| Line 21: | Line 21: | ||
= MinnowBoard Bug Triage Searches = | = MinnowBoard Bug Triage Searches = | ||
== | == Non-Prioritized Bugs == | ||
{{#bugzilla: | {{#bugzilla: | ||
|status=!(RESOLVED,VERIFIED,CLOSED) | |status=!(RESOLVED,VERIFIED,CLOSED) | ||
|hardware=MinnowBoard | |hardware=MinnowBoard, MinnowBoard-MAX | ||
|priority=Undecided | |priority=Undecided | ||
|severity=!janitors | |severity=!janitors | ||
| Line 36: | Line 36: | ||
|status=!(RESOLVED,VERIFIED,CLOSED) | |status=!(RESOLVED,VERIFIED,CLOSED) | ||
|hardware=MinnowBoard | |hardware=MinnowBoard | ||
|severity=!janitors | |severity=!janitors | ||
|columns=id,summary,severity,priority,milestone,to,status,whiteboard,estimated | |columns=id,summary,severity,priority,milestone,to,status,whiteboard,estimated | ||
Revision as of 18:28, 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
| ID | Summary | Severity | P | Milestone | Assignee | Status | Whiteboard | E |
|---|---|---|---|---|---|---|---|---|
| 0 |
MB Open Bugs
| ID | Summary | Severity | P | Milestone | Assignee | Status | Whiteboard | E |
|---|---|---|---|---|---|---|---|---|
| 0 |
MBX Open Bugs
| ID | Summary | Severity | P | Milestone | Assignee | Status | Whiteboard | E |
|---|---|---|---|---|---|---|---|---|
| 0 |
