FeaturePlanningProcess

Differences between revisions 1 and 2
Revision 1 as of 2006-11-07 00:50:16
Size: 841
Editor: 207
Comment: create
Revision 2 as of 2006-11-07 01:53:34
Size: 1486
Editor: 207
Comment:
Deletions are marked like this. Additions are marked like this.
Line 19: Line 19:
For each release, the Technical Board will establish high-level themes (on the order of three) which indicate the primary directions Ubuntu will pursue. These should be discussed at the developer summit for the prior release, six months before development of the target release begins.
Line 20: Line 21:
At the corresponding mid-release sprint, these themes will be finalized, and the Board, together with the development team, will generate feature ideas based on them. These should be close to the granularity of feature specifications, and will be used as input for the planning process for the next developer summit (which should already be in progress).

Please check the status of this specification in Launchpad before editing it. If it is Approved, contact the Assignee or another knowledgeable person before making changes.

  • Launchpad entry: none yet

  • Packages affected:

Summary

This specification describes a process by which new Ubuntu features are to be conceived, selected for a release, design and implemented.

Rationale

Historically, this process has been conducted informally as needed among some members of the Technical Board. In order to make it more rigorous and transparent, we want to make it an official responsibility of the Board and conduct it according to a regular schedule.

Process

For each release, the Technical Board will establish high-level themes (on the order of three) which indicate the primary directions Ubuntu will pursue. These should be discussed at the developer summit for the prior release, six months before development of the target release begins.

At the corresponding mid-release sprint, these themes will be finalized, and the Board, together with the development team, will generate feature ideas based on them. These should be close to the granularity of feature specifications, and will be used as input for the planning process for the next developer summit (which should already be in progress).


CategorySpec

FeaturePlanningProcess (last edited 2008-08-06 16:39:48 by localhost)