Bug Triage
From Yocto Project
Jump to navigationJump to search
THIS PAGE IS OBSOLETE
Please use the new triage page at https://dashboard.yoctoproject.org/bugtriage/.
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.
Roles
- Call facilitator: Stephen Jolley (sjolley.yp.pm@gmail.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
- Thursdays at 07:30 Pacific Time (15:30 GMT)
- Zoom Call Link (454-367-603 277925)
- Review security issues
- Review Queries
- State number, title, and owner
- Owner makes any modifications
- Assign owner, target milestone, and priority.
- Opens
- Collect opens
- Discuss opens
Bug Triage Order
- Security Issues
- Non-Prioritized Bugs and Non Targeted Bugs
- Autobuilder issues (graphical report (valkyrie))
- High Enhancements/Bugs
- Medium+ 5.2 Unassigned Enhancements/Bugs
- Medium+ 5.99 Unassigned Enhancements/Bugs
- NEEDINFO
- Reopened
- Old Milestone
- Future & 5.99 Milestones
- Note/Suggestion for the Weekly Triage Meeting: Open the first link in a new browser window and then each additional link in a new tab in that new window. Close the new window when the triage meeting is done.
Bug Criteria
- Priority-Severity
- High: Two Week - shouldn't slip to next milestone without review by Triage team.
- Medium+: Milestone Target Required
- Medium: Nice to have for milestone, should have for release
- Low: Nice to have, but no urgency
- Future bugs and enhancements are a good idea to do, but not able in the near term to get fixed or done.
- If you want to work on them, please talk first to the existing owner or change the ownership to yourself if unassigned or newcomer.
- Note: we have a special owner - newcomer@yoctoproject.org - which we think would be great opportunities for a newcomer to open source to start learning on.
- If you want to work on them, please talk first to the existing owner or change the ownership to yourself if unassigned or newcomer.
- Special Case: Medium+ and Future Enhancement or Bug - These are a good idea and important to do, but not currently scheduled at this time.
- If you want to work on them, please talk first to the existing owner or change the ownership to yourself if unassigned or newcomer.
- Note: we have a special owner - newcomer@yoctoproject.org - which we think would be great opportunities for a newcomer to open source to start learning on.
- If you want to work on them, please talk first to the existing owner or change the ownership to yourself if unassigned or newcomer.
- For more details see the wiki Bugzilla Configuration and Bug Tracking
Bug Status Dashboards
Weekly - https://wiki.yoctoproject.org/charts/combo.html
Daily - https://wiki.yoctoproject.org/charts/daily/combo.html
