Feature freeze adjustment to manage dependencies better

Registered by Kate Stewart on 2011-05-06

By splitting up the FeatureFreeze from being monolithic into classes of packages, we can manage the risk of incorporating changes into the release, and maximize the development time for bulk of the distribution.

Areas of increasing risk:
- "ToolchainFreeze" - for gnu toolchain - ABI changes in particular.
- "PlumbingFreeze" - for packages that have significant dependency chains, and need time to stabilize. List of packages to be defined by FeatureDefinitionFreeze, possibly use "core" seed as guidance?
- "FeatureFreeze" - for rest of packages (traditional definition).

Blueprint information

Status:
Not started
Approver:
Ubuntu Release Team
Priority:
High
Drafter:
Kate Stewart
Direction:
Approved
Assignee:
Kate Stewart
Definition:
Drafting
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

(?)

Work Items