This repository has been archived by the owner on Apr 24, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 412
Bug triage
rpaquay edited this page Nov 5, 2014
·
6 revisions
- Ensure there are no "blind spots" wrt to incoming bugs that need to be addressed in the current milestone.
Each bug triage session:
- Look at the list of bugs that 1) don't have a milestone and 2) where bug id > bug id of last bug looked at in the previous session
- "Look" merely means "does this bug look serious enough we need to address it in the current milestone". We don't need to investigate deeply, or assign a label, milestone, etc.
- As the end of the session, write down the last bug id looked at, so that the next session can restart where it left.
Current bug id (as of 11/05/2014): #3699
Request to look at bugs with no milestone sorted from oldest to newest:
- make sure all incoming issues are addressed
- make sure critical ones were addressed or investigated
- make sure current/upcoming milestone does not clogged with issues
- make sure tracker doesn't get clogged with issues
Issues are tracked/triaged in the weekly triage meeting, time boxed to 25 min, where the team
- aggressively closes incoming issues we don't think are going to be addressed. Note: give thanks to issue creator for the feedback!
- uses the milestone 'later' tag as a way to ensure that issues are tiraged. Issues are either an active milestone, in later, or closed.
- triages critical issues into the current (or maybe next) milestone, ensuring the issue is assigned to an owner to look at it.
Notes from 1st weekly triage:
- Look at list of issues without milestone
- Close bug
- Assign bug to someone for investigate in current milestone
- Move bug to "later" milestone, and assign one/more labels (bug, enhancement, etc.)
- Invite Prashant
- Investigate integration of pivotaltracker with github...
- Need owner for mobile issues...