Jump to: navigation, search

Difference between revisions of "StableBranchRelease"

 
Line 6: Line 6:
 
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.
 
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.
+
The [[ReleaseTeam]] is responsible for all [[OpenStack]] release deliveries, but [[markmc]] will join the [[ReleaseTeam]] 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]].
 
Below is the checklist of steps required to carry out this release, heavily based on [[ReleaseTeam/HowToRelease]].
Line 22: Line 22:
  
 
  Giving <code><nowiki>glance-2011.3.1~20120109.10803.tar.gz</nowiki></code>. Open questions:
 
  Giving <code><nowiki>glance-2011.3.1~20120109.10803.tar.gz</nowiki></code>. Open questions:
−
* Question: <code><nowiki>REVNOPREFIX=r</nowiki></code> or not?
+
# Add all bugs fixed on stable/diablo to the Diablo series in launchpad and assign to a newly created <code><nowiki>2011.3.1</nowiki></code> target. The stable team will be made the release for the diablo series (with the release team added to the stable team, to assist) and the release manager will accept bugs nominated for the diablo series. Bugs will be marked as [[FixCommitted]] in diablo when they are accepted onto stable/diablo. (Note: we need some launchpad scripting here)
−
* Question: add empty <code><nowiki>milestone/nova-diablo</nowiki></code> to avoid <code><nowiki>NOMILESTONE=true</nowiki></code>?
 
−
* Question: use e.g. <code><nowiki>rc1</nowiki></code> for <code><nowiki>milestone/nova-diablo</nowiki></code>
 
−
If yes, no, yes: <code><nowiki>glance-2011.3.1~rc1~20120109.r10803.tar.gz</nowiki></code>.
 
−
# Add all bugs fixed on stable/diablo to the Diablo series in launchpad and assign to a newly created <code><nowiki>2011.3.1</nowiki></code> target. Open questions:
 
−
#* Question: who can create the target and accept the bugs on Diablo?
 
−
(Note: we need some launchpad scripting here)
 
 
# Call for testing
 
# Call for testing
 +
# When the stable team feel feel the release is ready, the release team obtains PTL approval and informs the PPB.
 
# Push a commit to stable/diablo which does:
 
# Push a commit to stable/diablo which does:
 
<pre><nowiki>
 
<pre><nowiki>

Revision as of 15:25, 10 January 2012

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 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:
  1. Add all bugs fixed on stable/diablo to the Diablo series in launchpad and assign to a newly created 2011.3.1 target. The stable team will be made the release for the diablo series (with the release team added to the stable team, to assist) and the release manager will accept bugs nominated for the diablo series. Bugs will be marked as FixCommitted in diablo when they are accepted onto stable/diablo. (Note: we need some launchpad scripting here)
  2. Call for testing
  3. When the stable team feel feel the release is ready, the release team obtains PTL approval and informs the PPB.
  4. 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.
Retrieved from "https://wiki.openstack.org/w/index.php?title=StableBranchRelease&oldid=11323"