Pranav Salunke f1e4bfeca8 Porting presentations to Sphinx/Hieroglyph
modifided tox.ini and requirements.txt to install
hieroglyph, added some changes in the styles
of the individual .rst files to support hiero

Change-Id: Id2674e593857470cf4efa0706a4fbda33813f374
2015-03-26 14:33:38 +01:00

2.8 KiB

OpenStack Release Cycle

<teacher name> <date>


Planning : Design

colleft

  • 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

colleft

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

image


Planning : Target

colleft

  • 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

colright

image


Implementation : Milestone

colleft

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

colright

image


Implementation : freezes

colleft

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

colright

image


Release Candidates

colleft

  • After the last milestone
  • file bugs about everything you find
  • prioritize bugs / bug triage
  • write documentation
  • fix as many bugs as you can

colright

image


Release candidate 1

colleft

  • 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

colright

image


Other release candidates

colleft

  • 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

colright

image


Release day

colleft

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

colright

image


Exercise

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