Jump to: navigation, search


Revision as of 20:20, 8 August 2013 by Apevec (talk | contribs) (Tag)

Stable Branch Releases

The openstack-stable-maint team rigorously applies the documented StableBranch principles and works hard to include appropriate bugfixes from master on the stable branch while limiting the risk of regressions. The intention is for releases published from the stable branch to be a safe source of fixes for high-impact user-visible issues.

The ReleaseTeam is responsible for all OpenStack release deliveries and apevec and adam_g coordinate releases from the stable branch. Stable branch releases are expected roughly every 8 weeks, depending on how many fixes are queued up.

You can see a history of these releases on the Releases page.

How To Release

Below is the checklist of steps required to carry out this release, heavily based on ReleaseTeam/HowToRelease.


Make sure the current versioning on the stable branch of each project is correct - e.g. the version in NOVA_VERSION is the same as the version you intend to release and FINAL = False. Note, Keystone is a little different and stores its version in setup.py. Note2: FINAL is not used since Grizzly.


Make sure the tarballs job in Jenkins is building tarballs correctly for each project e.g. check here for Nova Grizzly that a tarball is being built from the stable branch each time a commit is pushed there.

NOTE OpenStack Networking project was renamed to Neutron but in stable/grizzly tarball filename stays quantum-2013.1*.tar.gz - take care of that during tarball upload!

Warn People

Discuss your plans for the release at the weekly project meeting.

Preferably set a date for the release immediately after the previous release.


Create a launchpad milestone for each project for the version you're planning to release.


Note: only project drivers can target bugs to a series so the release manager needs to find bugs tagged with in-stable-grizzly and target them.

  1. Gather a list of bugs fixed since the previous release e.g.
$> git log --no-merges --topo-order 2013.1.2.. | grep -i '\(bug\|lp\)[: #]*' | sed 's/.*\(1[0-9][0-9][0-9][0-9][0-9][0-9]\).*/\1/' > nova-bugs.txt
  1. Sanity check the list of bugs. Check that each has had a patch proposed to the stable branch
$> python showbugs.py $(cat nova-bugs.txt)
  1. Nominate those bugs for the series
$> python nominate.py nova grizzly $(cat nova-bugs.txt)
  1. Target those bugs at the milestone
$> python target.py nova grizzly 2013.1.3 $(cat nova-bugs.txt)
  1. Review the list of bugs targeted to the milestone and fixup Importance and Assignee fields e.g. https://bugs.launchpad.net/nova/+milestone/2013.1.3
  2. Review bugs tagged with in-stable-grizzly and target them appropriately if they haven't already been targeted. Don't forget to remove the tag. e.g. a query for nova
  3. Review bugs tagged with grizzly-backport-potential, untag fixes already backported and consider backporting important ones. e.g. a query for nova.
  4. Check to see if any bugs were nominated for the series
  5. Look at open reviews and make sure the corresponding bugs are targeted. e.g. query for nova.

Call For Testing

Call for testing, see this example


  1. Tag the release:
$> git tag -s 2013.1.3
$> git push gerrit tag 2013.1.3

Close bugs

  1. Mark all FixCommitted bugs as FixReleased. With a small change:
+series = proj.getSeries(name='folsom')
+bugtasks = series.searchTasks(status='Fix Committed', omit_targeted=False)
we can use process-fixcommitted-bugs.py:
$> python ./process-fixcommitted-bugs.py nova --onlymilestone 2012.2.3 --fixrelease

Upload The Release

Using https://github.com/ttx/openstack-releasing

  1. Upload the release:
$> python ./upload_release.py nova 2012.2.3


  1. Update SecurityAdvisories/Folsom
  2. Write release notes like ReleaseNotes/2012.1.3
  3. Send release announcement like this example.
  4. Update Releases
  5. Update Get_OpenStack#Get_the_source_code

Rinse, Repeat

  1. Open development for the next release by increasing the micro version in e.g. NOVA_VERSION and setting FINAL = False NOTE since Grizzly only bump version in setup.py e.g. https://review.openstack.org/#/q/I130528ae946e8888d35c25e468b4ea6ac29db0cf,n,z
  2. Decide on date for next release, create milestones

Planned stable/grizzly releases

 2013.1.2 Jun 6
 2013.1.3 Aug 8
 2013.1.4 Oct 10
 2013.1.5 - last planned, date TBD, after H release