Bug statistics

Registered by Henrik Nilsen Omma on 2007-10-04

Identify bug statistics that will be useful to the Ubuntu team during the cycle to drive quality improvements and assist during release periods. Automate the gathering and dissemination of these stats.

Agenda:

 * What stats to we want?
  * Useful categories and states of bugs
  * Derived values (time in New state, time to closed, etc.)
 * Maintaining scripts:
  * where do they run and how can people contribute?
  * transition from l-p-b to XML-RPC; when and how?
 * Displaying bug stats - how should the results be presented
  * Should we move on from the current tabbed display, which has various layout limitations
  * Consider providing the data separate from the layout as an XML feed (is RSS or similar suitable?)

Blueprint information

Status:
Complete
Approver:
Henrik Nilsen Omma
Priority:
High
Drafter:
Pedro Villavicencio
Direction:
Approved
Assignee:
Brian Murray
Definition:
Approved
Series goal:
None
Implementation:
Implemented
Milestone target:
None
Started by
Henrik Nilsen Omma on 2007-10-25
Completed by
Henrik Nilsen Omma on 2008-05-08

Related branches

Sprints

Whiteboard

A good chunk of this has been implemented with a range of bug graphs and stats. More work is needed on presenting the information concisely and using it actively in guiding triage and development.

(?)

Work Items

Dependency tree

* Blueprints in grey have been implemented.