openstack/training-guides

Stefano Maffulli 6d66d0d550 First try at adding Upstream Training material

Work in progress

Implements Blueprint: merge-upstream-university-training

Change-Id: I4d4c7f08d8c599178df2cbcf3969bc739ca6784c

2014-06-18 12:51:49 -07:00

2.2 KiB

Raw Blame History

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

Planning : Discuss

With our peers
feedback and comments
create the corresponding blueprint
4 weeks, Design Summit on the third week

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

Implementation : Milestone

pushed to our Gerrit review
weeks before the milestone publication date.
milestone-proposed branch
feature-frozen

Implementation : freezes

Feature proposal freeze
String freeze
Feature freeze

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

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

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

Release day

last published Release Candidate
published collectively as the OpenStack release

Exercise

Based on the Icehouse release schedule find the URL of a document or a patch that belongs to each of the steps.