Feature Freezes: When Enough Is Enough

Registered by Stephen Michael Kellat

As highlighted during IRC discussion on the day before release of 13.04 (see http://irclogs.ubuntu.com/2013/04/24/%23ubuntu-release.html#t21:13 ) there is a need to discuss when enough is enough. When should things land in a release cycle? What should deadline enforcement look like? When features and other changes are proposed to be landed during the last two weeks (see for example: https://bugs.launchpad.net/unity/+bug/1169238 ) should there be a point where it is said that "Enough Is Enough"? After changes to the support cycle length, what is required to ensure compliance with deadlines set by the Release Managers so that a release happens with minimal incident?

Blueprint information

Status:
Complete
Approver:
None
Priority:
Undefined
Drafter:
None
Direction:
Needs approval
Assignee:
None
Definition:
Obsolete
Series goal:
None
Implementation:
Blocked
Milestone target:
None
Started by
Stephen Michael Kellat
Completed by
Stephen Michael Kellat

Related branches

Sprints

Whiteboard

I don't think there's any mystery here. We have a schedule and teams that choose to work out of process aren't certain to get in. I'm not sure we need a spec for this.

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.