Server papercuts

Registered by Thierry Carrez on 2010-04-28

During the Lucid cycle we ran a Server papercuts project to find and fix usability bugs in Ubuntu Server. What changes should be applied to the process, how long should it run (and should it start early enough to allow new features to be part of it), what targets should we have ?

Blueprint information

Status:
Complete
Approver:
Jos Boumans
Priority:
Medium
Drafter:
Thierry Carrez
Direction:
Approved
Assignee:
Thierry Carrez
Definition:
Approved
Series goal:
Accepted for maverick
Implementation:
Implemented
Milestone target:
milestone icon ubuntu-10.10-beta
Started by
Thierry Carrez on 2010-05-28
Completed by
Thierry Carrez on 2010-08-31

Related branches

Sprints

Whiteboard

Status:
Beta cycle done: https://launchpad.net/server-papercuts/+milestone/maverick-beta

Complexity:
maverick-alpha-3: 1
ubuntu-10.10-beta: 1

Work items for maverick-alpha-2:
[ttx] Reconsider lucid refused candidates: DONE
Announce alpha2 cycle (2010-05-22): DONE
Define list of alpha2 targets (2010-06-01): DONE
Assign/Fix alpha2 targets: DONE
Generate candidates for bad-recommends theme: DONE
Status update for alpha2 cycle (2010-06-15): DONE
Announce alpha3 cycle (2010-06-19): DONE
Analyze bad-recommends candidates: DONE
Define list of alpha3 targets (2010-06-29): DONE

Work items for maverick-alpha-3:
Status update for alpha3 cycle (2010-07-13): DONE
UDW session: DONE
Assign/Fix alpha3 targets: DONE
[mathiaz] Fix alpha3 targets: DONE
[mathiaz] Review james-pages alpha3 papercut: DONE
Announce beta cycle (2010-07-24): DONE
Define list of beta targets (2010-08-03): DONE

Work items for ubuntu-10.10-beta:
[jib] Status update for beta cycle (2010-08-17): DONE
Assign/Fix beta targets: DONE
Maverick retrospective (2010-08-31): DONE

mathiaz review - 20100526:
  * I don't see any WI defined for actually fixing the bugs. Given that there is a goal set for the number of bugs for each cycle and that each bug should take up to 2 hours to fix it should be possible to add WI for fixing bugs.
    * Sure, I'll link the bugs when approved. Using bug links will avoid redundancy in bug assignation -- ttx

jib review / 20100526:

  * I'd like to see work items for every bug or bugs linked so we can track them in the WI tracker
  * Suggested assignees: ttx, assigning individual cuts to team

  * Suggested priority: 1/high

  * Suggested Subcycle: Every

(?)

Work Items