Development/Release Process

Registered by Jesse Andrews on 2011-04-18

This blueprint has been superseded. See the newer blueprint "Release schedule for Diablo and after" for updated plans.

OpenStack compute is still evolving at a rapid pace. 3 months is both too long (a lot changes between releases) and too short (supporting 4 releases a year is a lot of work).

To that end I propose that we move to a model of less frequent supported releases (6+ months) with frequent intermediate milestone releases (every 6 weeks). 6 weeks allows teams that use agile sprints of 2 or 3 weeks to sync with milestone releases.

Google chrome has had a successful at adopting a short development process with release trains - documented here: https://docs.google.com/present/view?id=dg63dpc6_4d7vkk6ch&pli=1 --- we should talk about adopting some of their practices that are applicable.

Blueprint information

Status:
Complete
Approver:
None
Priority:
Undefined
Drafter:
None
Direction:
Needs approval
Assignee:
None
Definition:
Superseded
Series goal:
None
Implementation:
Unknown
Milestone target:
None
Completed by
Thierry Carrez on 2011-04-18

Related branches

Sprints

Whiteboard

This is already covered by two other discussions that will occur on Wednesday morning: one on release schedule (3 months vs. other options) and one on branching model (us vs. kernel vs. NVIE vs. Chrome), so I think we have this one covered.

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.