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.
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
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.
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-folsom and target them.
- Gather a list of bugs fixed since the previous release e.g.
$> git log --no-merges --topo-order 2012.2.1.. | grep -i '\(bug\|lp\)[: #]*' | sed 's/.*\(1[0-9][0-9][0-9][0-9][0-9][0-9]\).*/\1/' > nova-bugs.txt
- 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)
- 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 folsom 2012.2.3 $(cat nova-bugs.txt)
- Review the list of bugs targeted to the milestone and fixup Importance and Assignee fields e.g. https://bugs.launchpad.net/nova/+milestone/2012.2.3
- Review bugs tagged with in-stable-folsom and target them appropriately if they haven't already been targeted. Don't forget to remove the tag. e.g. a query for nova
- Review bugs tagged with folsom-backport-potential, untag fixes already backported and consider backporting important ones. e.g. a query for nova.
- Check to see if any bugs were nominated for the series
- 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
- Push a commit to branch which does:
FINAL = Trueto nova, cinder, quantum and horizon e.g. https://review.openstack.org/#/q/Ic83a1c1617ad74b931f54f1755bc9dcecfe2c527,n,z Keystone and Glance do not have FINAL variable.
- Tag the release:
$> git tag -s 2012.2.3 $> git push gerrit tag 2012.2.3
+series = proj.getSeries(name='folsom') +bugtasks = series.searchTasks(status='Fix Committed', omit_targeted=False)
we can use
$> python ./process-fixcommitted-bugs.py nova --onlymilestone 2012.2.3 --fixrelease
Upload The Release
- Upload the release:
$> python ./upload_release.py nova 2012.2.3 --tarball=stable-folsom
- Update SecurityAdvisories/Folsom
- Write release notes like ReleaseNotes/2012.1.3
- Send release announcement like this example.
- Update Releases
- Update Get_OpenStack#Get_the_source_code
- Open development for the next release by increasing the micro version in e.g.
FINAL = False
- Decide on date for next release, create milestones