QA

Revision 8 as of 2008-05-20 07:10:05

Clear message

UDS Intrepid QA Report

[:UDS-Intrepid/Report:back to the reports index page]

Place in this section bullet points of specific intended outcomes for the 8.10 development cycle.

See [:QATeam/KernelBugMigration].

Spec: foo

How can we measure it?
- some date transitions are recorded in Launcpad
  - available on a per task basis
    - date-left-new - particularly useful
      - this is the first time the bug's state changed
    - date-confirmed
    - date-triaged
    - date-incomplete
    - date-triaged - particularly useful
    - date-fixcommited
    - date-fix-released - particularly useful
    - date-closed
    - date-inprogress
    - date-assigned
    - date-created
      - the date-created for a bug watch would show when the upstream task was created
      - the activity log, bug-watch-updater first comment, shows when the watch was created
  - available for the bug in general
    - date reported
    - date updated
  - missing?
    - date importance set - in activity log but potentially hard to parse
  - look at the average or median response times over a 1,3,6 month period
  - a new tool in the bughelper suite could be used to show time in state statistic infromation
How can we improve it?
- making information publicly available
Display on per-package status page
- also combine some packages for example linux-source, linux-restricted-modules, linux-ubuntu-modules, linux-backports-modules
Display on a per repository basis
Display on a per team basis using something like https://bugs.launchpad.net/~ubuntu-printing/+packagebugs
- these are packages that a team is subscribed to

Spec: foo

Case 1: World breaking regressions in stable or late devel version
- Using the critical importance with an escalation bot
Case 2: Important bugs that need be made more prominent before release
- Formal and informal escalation paths within the QA team