
Work in progress Implements Blueprint: merge-upstream-university-training Change-Id: I4d4c7f08d8c599178df2cbcf3969bc739ca6784c
125 lines
2.2 KiB
ReStructuredText
125 lines
2.2 KiB
ReStructuredText
OpenStack Release Cycle
|
|
=======================
|
|
|
|
OpenStack Upstream Training
|
|
---------------------------
|
|
|
|
<teacher name>
|
|
<date>
|
|
|
|
----
|
|
|
|
Planning : Design
|
|
=================
|
|
|
|
- Planning stage is at the start of a cycle
|
|
- take a step back
|
|
- focus on what we want to do for the next one
|
|
|
|
.. image:: ./_assets/01-01-release.png
|
|
|
|
----
|
|
|
|
Planning : Discuss
|
|
==================
|
|
|
|
- With our peers
|
|
- feedback and comments
|
|
- create the corresponding blueprint
|
|
- 4 weeks, Design Summit on the third week
|
|
|
|
.. image:: ./_assets/01-01-release.png
|
|
|
|
----
|
|
|
|
Planning : Target
|
|
=================
|
|
|
|
- file new blueprints
|
|
- set a target milestone
|
|
- when in the cycle they intend to complete it
|
|
- PTLs triage the submitted blueprints and sets Priority
|
|
|
|
.. image:: ./_assets/01-01-release.png
|
|
|
|
----
|
|
|
|
Implementation : Milestone
|
|
==========================
|
|
|
|
- pushed to our Gerrit review
|
|
- weeks before the milestone publication date.
|
|
- milestone-proposed branch
|
|
- feature-frozen
|
|
|
|
.. image:: ./_assets/01-01-release.png
|
|
|
|
----
|
|
|
|
Implementation : freezes
|
|
========================
|
|
|
|
- Feature proposal freeze
|
|
- String freeze
|
|
- Feature freeze
|
|
|
|
.. image:: ./_assets/01-01-release.png
|
|
|
|
|
|
----
|
|
|
|
Release Candidates
|
|
==================
|
|
|
|
- After the last milestone
|
|
- file bugs about everything you find
|
|
- prioritize bugs / bug triage
|
|
- write documentation
|
|
- fix as many bugs as you can
|
|
|
|
.. image:: ./_assets/01-01-release.png
|
|
|
|
----
|
|
|
|
Release candidate 1
|
|
===================
|
|
|
|
- Between the last milestone and the RC1
|
|
- stop adding features and concentrate on bugfixes
|
|
- Once all the release-critical bugs are fixed, we produce the first - - - release candidate for that project (RC1)
|
|
- used as-is as the final release
|
|
|
|
.. image:: ./_assets/01-01-release.png
|
|
|
|
----
|
|
|
|
Other release candidates
|
|
========================
|
|
|
|
- regressions and integration issues
|
|
- new release-critical bugs
|
|
- (RC2), with bugs targeted to it
|
|
- merged in the master branch first
|
|
- repeated as many times as necessary
|
|
|
|
.. image:: ./_assets/01-01-release.png
|
|
|
|
----
|
|
|
|
Release day
|
|
===========
|
|
|
|
- last published Release Candidate
|
|
- published collectively as the OpenStack release
|
|
|
|
.. image:: ./_assets/01-01-release.png
|
|
|
|
----
|
|
|
|
Exercise
|
|
========
|
|
|
|
|
|
Based on the Icehouse release schedule find the URL of a document or a patch that belongs to each of the steps.
|
|
|