Efficient bug handling workflow/management
At the last UDS we discussed and adjusted our approach to bug triaging/fixing prioritization (https:/
Blueprint information
- Status:
- Complete
- Approver:
- Rick Spencer
- Priority:
- Medium
- Drafter:
- Martin Pitt
- Direction:
- Needs approval
- Assignee:
- Canonical Desktop Team
- Definition:
- Approved
- Series goal:
- Accepted for lucid
- Implementation:
-
Implemented
- Milestone target:
-
lucid-alpha-3
- Started by
- Martin Pitt
- Completed by
- Martin Pitt
Related branches
Related bugs
| Bug #333521: Enable bugs expiration for Ubuntu | Fix Released |
| Bug #487900: retracer should subscribe ubuntu-bugcontrol team to bugs w/ lots of dups | Fix Released |
Whiteboard
Work items:
[pitti] apport symptomps: Generate default bug title so that "proposed duplicates" have a chance to work: DONE
[pitti] identify package hooks which are suitable for generating a default bug title: DONE
[pitti] totem package hook: Generate default bug title so that "proposed duplicates" have a chance to work: DONE
[cr3] provide list of types of problems that we should make symptoms for: DONE
Improve/fine tune parameters for "bug heat": DONE
[rick-rickspencer3] Make bughugger display results of long running queries that are run by cron jobs on servers: DONE
[rick-rickspencer3] Upstream launchpadlib pygtk components: POSTPONE
[bryceharrington] generalize bug searching scripts for other areas of Ubuntu: DONE
[brian-murray] turn batch bug action scripts into bughugger plugins: DONE
Work items for ubuntu-10.04:
[seb128] Disable lp-i menu item for reporting a bug in the stable release; only leave it for the development release: DONE
[pvillavi] Generalize hug day concept and involve the community more: "15 minutes a day ... please triage these three bugs": DONE
[pvillavi] Adopt a package for triaging, give triagers a sense of ownership: DONE
[deryck] Change Launchpad bug interface to setting expectations and next steps (after a user has submitted a bug): DROPPED
pitti, 2010-01-20: converted bug expiry work item into a linked bug; subscribed Marc Tardif since he has a work item here
pitti, 2010-02-16: unlike symptoms, package hooks are generally not suitable for predicting what the error is, and thus what a good default bug title is; only exception is the totem hook, which is very similar to the audio symtpom.
cr3, 2010-02-18: Initial list of symptoms we should eventually have, see below. They are primarily intended as an extensive list of symtpoms I could imagine. I would propose that the next phase should be to refine this list and then elaborate the user experience associated with each. For example, whether the user should be prompted or not. And, if prompted, what the questions should be.
cr3/pitti: https:/
pitti, 2010-04-27: Dropped LP bug interface change, it's filed in LP and being worked on, but not a desktop spec.
