StableBranchRelease

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 markmc coordinates 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.

1. Versioning: 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.
2. Make sure the tarballs job in Jenkins is building tarballs correctly for each project e.g. check here for nova that a tarball is being built from the stable branch each time a commit is pushed there.
3. Discuss your plans for the release at the weekly project meeting.
4. Create a launchpad milestone for each project for the version you're planning to release.
5. Add all bugs fixed on the stable branch to the appropriate launchpad and target to the milestone you've just created.

# Gather a list of bugs fixed since the previous release
$> git log  2012.2..origin/stable/folsom | grep '[0-9][0-9][0-9][0-9][0-9][0-9]' | grep -v '^\(commit \|Merge\)' | grep -v -i '\(cherry[ -]picked\|Change-Id\|bugzilla\)' | sed 's/[^0-9]*\(1\?[0-9][0-9][0-9][0-9][0-9][0-9]\)[^0-9]*/\1/g' | sort | uniq > nova-bugs.txt
# Sanity check that list of bugs
$> python showbugs.py $(cat nova-bugs.txt)
# Nominate those bugs for the series
$> python nominate.py nova essex $(cat nova-bugs.txt)
# Target those bugs at the milestone
$> python target.py nova essex 2012.1.3 $(cat nova-bugs.txt)

1. Call for testing, see this example
2. When the stable team feel feel the release is ready, the release team obtains PTL approval and informs the TC.
3. Push a commit to branch which does:FINAL = True
4. Tag the release:

$> git tag -s 2012.1.3
$> git push gerrit tag 2012.1.3

1. Mark all FixCommitted bugs as FixReleased. With a small change:

+series = proj.getSeries(name='essex')
+bugtasks = series.searchTasks(status='Fix Committed', omit_targeted=False)

we can use process-fixcommitted-bugs.py:

$> python ./process-fixcommitted-bugs.py nova --onlymilestone 2012.1.3 --fixrelease

1. Upload the release:

$> ./upload_release.py nova 2012.1.3 20121012.13710

1. Update SecurityAdvisories/Folsom
2. Write release notes like ReleaseNotes/2012.1.3
3. Send release announcement like this example.
4. Open development for the next release by increasing the micro version in e.g. NOVA_VERSION and setting FINAL = False