Jump to: navigation, search

StableBranchRelease

Revision as of 13:59, 9 January 2012 by Markmc (talk)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Releasing From The Stable Branch

Since the release of Diablo on 2011-09-22, the stable/diablo branches of nova and glance have accumulated roughly 80 and 20 fixes respectively. The openstack-stable-maint team have rigorously applied the documented StableBranch principles and have worked hard to include appropriate bugfixes from master while limiting the risk of regressions.

At least Fedora and Ubuntu have been updating their packages from the stable branch and haven't seen any regressions. We feel the time is long past for OpenStack to prepare a 2011.3.1 update release from the branch.

The ReleaseTeam is responsible for all OpenStack release deliveries, but markmc will join the ReleaseTeam to specifically to help prepare the diablo update release.

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

  1. Versioning: push a change to master and stable/diablo to add a REVISION field to {NOVA,GLANCE}_VERSION e.g.
GLANCE_VERSION = ['2011', '3', '1']
YEAR, COUNT, REVISION = GLANCE_VERSION
Also, make FINAL = False on stable/diablo, for now.
  1. Set up a tarballs job in Jenkins to build stable/diablo tarballs. It appears that tarball_script.sh will work just fine with:
BRANCH=diablo
NOMILESTONE=true 
Giving glance-2011.3.1~20120109.10803.tar.gz. Open questions:
  • Question: REVNOPREFIX=r or not?
  • Question: add empty milestone/nova-diablo to avoid NOMILESTONE=true?
  • Question: use e.g. rc1 for milestone/nova-diablo
If yes, no, yes: glance-2011.3.1~rc1~20120109.r10803.tar.gz.
  1. Add all bugs fixed on stable/diablo to the Diablo series in launchpad and assign to a newly created 2011.3.1 target. Open questions:
    • Question: who can create the target and accept the bugs on Diablo?
(Note: we need some launchpad scripting here)
  1. Call for testing
  2. Push a commit to stable/diablo which does:
FINAL = True
and once the tarball has been generated, push:
GLANCE_VERSION = ['2011', '3', '2']
FINAL = False
  1. Tag the release:
$> git tag -s 2011.3.1
$> git push gerrit tag 2011.3.1
  1. Mark all Diablo FixCommitted bugs as FixReleased. (process-fixcommitted-bugs.py will help here)
  2. Upload the release:
$> ./upload_release.py glance 2011.3.1 20120109.10803
  1. PPA updates. (Delegate to openstack-ppa team?)
  2. Send release announcement.