Priorities for development release maintenance

Registered by Colin Watson on 2011-10-20

The Ubuntu Engineering team in Canonical is committing a rotation of developers to work solely on development release maintenance for a month or two at a time, with the goal of keeping the development release buildable, installable, and upgradeable at all times in order to allow other developers to work with fewer interruptions. What should our priorities be? How should we organise ourselves? Given the alignment between this and e.g. the historical activities of MOTU, how can we build community participation or link into existing activities?

Blueprint information

Status:
Complete
Approver:
Steve Langasek
Priority:
High
Drafter:
Colin Watson
Direction:
Approved
Assignee:
Colin Watson
Definition:
Approved
Series goal:
None
Implementation:
Informational Informational
Milestone target:
None
Started by
Steve Langasek on 2011-11-18
Completed by
Steve Langasek on 2011-11-18

Related branches

Sprints

Whiteboard

(?)

Work Items