Editing Bug Triage
Bold textItalic textInternal linkExternal link (remember http:// prefix)Level 2 headlineEmbedded fileFile linkIgnore wiki formattingYour signature with timestampHorizontal line (use sparingly)
Goal
The output of the bug IoT Ref Kit 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.
Roles
- Call facilitator: Stephen K. Jolley (stephen.k.jolley@intel.com)
- Ensure we keep to the agenda, don't rathole on bug resolution, and stay within our time block.
- Team Leads should pre-triage bugs for their areas of responsibility. Some guidelines on what they should/shouldn't do are:
- a) Pre-triage should happen in the presence of the appropriate team lead,
- b) The bugs being pre-triaged should be the responsibility of the team in question.
- c) The pre-triage team should be confident when dis-positioning the bugs, taking into account the individual's workload.
- d) If the bug raises any doubt or needs information prior, defer it to the main bug triage team.
- e) To insure a bug is triaged by the main bug triage team; set its priority to Undecided.
Agenda
- Review Queries
- State number, title, and owner
- Owner makes any modifications
- Assign owner, target milestone, and priority.
- Opens
- Collect opens
- Discuss opens
Bug Criteria
- Priority-Severity
- High: Two Week
- Medium+: Milestone
- Medium: Nice to have for milestone, should have for release
- Low: Nice to have, but no urgency
Bug Product Searches
Yocto Bug Triage Searches
Non-Prioritized Bugs
| ID | Summary | Severity | P | Milestone | Assignee | Status | Whiteboard | E |
|---|
| | 0 | | | | | | | |
Non-Targeted Bugs
| ID | Summary | Severity | P | Milestone | Assignee | Status | Whiteboard | E |
|---|
| | 0 | | | | | | | |
Unassigned Bugs
| ID | Summary | Severity | P | Milestone | Assignee | Status | Whiteboard | E |
|---|
| 11466 | TPM 2.0 support (under qemu) | enhancement | Medium | Future | Unassigned | IN PROGRESS IMPLEMENTATION | | 3 |
| | 1 | | | | | | | |
New This Week
| ID | Summary | Severity | P | Milestone | Assignee | Status | Whiteboard | E |
|---|
| | 0 | | | | | | | 0 |
Medium+ Enhancements/Bugs
| ID | Summary | Severity | P | Milestone | Assignee | Status | Whiteboard | E |
|---|
| | 0 | | | | | | | |
High Enhancements/Bugs
| ID | Summary | Severity | P | Milestone | Assignee | Status | Whiteboard | E |
|---|
| | 0 | | | | | | | |
Bugs and Enhancements by Owner !(Future, 2.4)
| ID | Summary | Severity | P | Milestone | Assignee | Status | Whiteboard | E |
|---|
| | 0 | | | | | | | |
NEEDINFO
| ID | Summary | Assignee | Status | Severity | P | Milestone | Modified | Whiteboard |
|---|
| | 0 | | | | | | | |
Re-Opened
| ID | Summary | Assignee | Status | Severity | P | Milestone | Whiteboard |
|---|
| | 0 | | | | | | |
Old Milestone
| ID | Summary | Assignee | Status | Severity | P | Milestone | Whiteboard |
|---|
| | 0 | | | | | | |
Future Dot Releases
| ID | Summary | Assignee | Status | Severity | P | Milestone | Whiteboard |
|---|
| | 0 | | | | | | |
