Bug Triage Automation with Arsenal

Registered by Bryce Harrington on 2011-05-05

Arsenal and python-launchpadlib-toolkit ("lpltk") are used by kernel, xorg, and other desktop teams for managing large inflows of bug reports. This session is for coordination of Arsenal development work for Oneiric.

Arsenal Development Planning
 * Automatic release tagging effectiveness
 * Migration of arsenal to using lpltk
 * Brian Murray's development work
 * Kernel team's development work
 * Bug upstreamer tool work
 * Need for better integration of web reports/graphs
 * Differentiating "actionable issues" and "help requests"
   + http://doctormo.org/2011/04/29/bugs-are-not-issues/
   + Old "new bug" processing script (rewrite?)
 * "Choose Your Own Adventure" style automatic guide?
   + For common classes of bugs, walk user through a Q&A process to narrow the bug down

Arsenal Features
 * Mechanical bug processing
   + Tagging / title fixing
   + Determining package to refile against
   + "Please retest"-style bulk updaters
 * Reports
   + "Workqueue report": http://www.bryceharrington.org/Arsenal/Reports/ubuntu-x-swat/workqueue-oneiric.html
   + "Fixed Upstream": http://www.bryceharrington.org/Arsenal/Reports/mozilla-bugs/upstream-fixed.html
   + "Bugs with Patches": http://www.bryceharrington.org/Arsenal/Reports/compiz/patches.html
 * Graphing / metrics tools
   + http://www.bryceharrington.org/Arsenal/Reports/ubuntu-x-swat/totals-natty-workqueue.svg
   + http://www.bryceharrington.org/Arsenal/Reports/ubuntu-x-swat/totals.svg

Blueprint information

Status:
Complete
Approver:
None
Priority:
Undefined
Drafter:
Bryce Harrington
Direction:
Needs approval
Assignee:
Bryce Harrington
Definition:
Obsolete
Series goal:
None
Implementation:
Informational Informational
Milestone target:
None
Completed by
Bryce Harrington on 2012-05-22

Related branches

Sprints

Whiteboard

bryce, 2011-05-17: Mostly this was an informational session to introduce Arsenal to people and to coordinate with Brian and Brad. However, due to the surprisingly large turnout at the session, a few tasks were identified that'd make Arsenal easier for more people to get into, but probably not worth sketching out a blueprint on.

(?)

Work Items

Work items:
[bryce] Complete migration of arsenal codebase to lpltk: TODO
[bryce] Set up website about Arsenal: TODO
[bryce] Review Brad Figg's kernel webpage scripts / stylesheets: DONE
[bryce] Figure out how to prevent bzr from erroring on pushes: DONE