openstack/training-guides
Code Issues Proposed changes
training-guides/doc/upstream-training/01-release-cycle.rst
Matjaz Pancur 747227bb04 Fix broken master repo 
Because of the new gating system (gate-training-guides-tox-slides), we need to
cleanup all existing RST files.

There is a small rendering problem with Landslide in the Upstream training
and all the Title slides (empty slides with only a Title). The check doesn't
like "empty" slides ("Document or section may not begin with a transition."),
Landslide deals with this by ignoring errors
(https://github.com/adamzap/landslide/issues/94), but our gating check does
not. I temporary changed all such slides to normal ones.

I also had to change training-guides/landslide.sh a bit (a quick hack so that
it works as expected).

Change-Id: I6c3ae06235e69c4a53741e74a5642d27083f4df0
2015-02-22 21:53:56 +01:00

2.8 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

image

Planning : Discuss

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

image

Planning : Target

  • file new blueprints and/or specs
  • set a target milestone
  • when in the cycle they intend to complete it
  • PTLs triage the submitted blueprints and set priority

image

Implementation : Milestone

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

image

Implementation : freezes

  • Feature freeze
    • new features will not be accepted, only fixes
  • Feature proposal freeze
    • not even proposals for features will be accepted
    • read: focus on bug-fixing
  • String freeze
    • all externally visible strings must be frozen
    • this helps the translation and documentation program

image

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

Release candidate 1

  • Between the last milestone and the RC1
  • stop adding features and concentrate on bug fixes
  • 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

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

Release day

  • last published release candidate
  • published collectively as the OpenStack release

image

Exercise

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