Jump to: navigation, search

Difference between revisions of "StableBranchRelease"

Line 12: Line 12:
 
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]].
  
−
# Versioning: make sure the current versioning on the stable branch of each project is correct - e.g. the version in <code><nowiki>NOVA_VERSION</nowiki></code> is the same as the version you intend to release and <code><nowiki>FINAL = False</nowiki></code>. Note, keystone is a little different and stores its version in <code><nowiki>setup.py</nowiki></code>.
+
=== Versioning ===
−
# Make sure the tarballs job in Jenkins is building tarballs correctly for each project e.g. check [http://tarballs.openstack.org/nova/?C=M;O=D 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.
+
Make sure the current versioning on the stable branch of each project is correct - e.g. the version in <code><nowiki>NOVA_VERSION</nowiki></code> is the same as the version you intend to release and <code><nowiki>FINAL = False</nowiki></code>. Note, keystone is a little different and stores its version in <code><nowiki>setup.py</nowiki></code>.
−
# Create a launchpad milestone for each project for the version you're planning to release.
+
 
−
# Add all bugs fixed on the stable branch to the appropriate launchpad and target to the milestone you've just created.
+
=== Tarballs ===
 +
 
 +
Make sure the tarballs job in Jenkins is building tarballs correctly for each project e.g. check [http://tarballs.openstack.org/nova/nova-stable-folsom.tar.gz here for nova] that a tarball is being built from the stable branch each time a commit is pushed there.
 +
 
 +
=== 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.
 +
 
 +
=== Milestones ===
 +
 
 +
Create a launchpad milestone for each project for the version you're planning to release.
 +
 
 +
=== Bugs ===
 +
 
 +
# Gather a list of bugs fixed since the previous release e.g.
 +
<pre><nowiki>
 +
$> 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
 +
</nowiki></pre>
 +
 
 +
# Sanity check the list of bugs. Check that each has had a patch proposed to the stable branch
 
<pre><nowiki>
 
<pre><nowiki>
−
# 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)
 
$> python showbugs.py $(cat nova-bugs.txt)
−
# Nominate those bugs for the series
+
</nowiki></pre>
 +
 
 +
# Nominate those bugs for the series  
 +
<pre><nowiki>
 
$> python nominate.py nova essex $(cat nova-bugs.txt)
 
$> 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)
 
 
</nowiki></pre>
 
</nowiki></pre>
  
−
# Call for testing, see [https://lists.launchpad.net/openstack/msg17332.html this example]
+
# Target those bugs at the milestone
−
# When the stable team feel feel the release is ready, the release team obtains PTL approval and informs the TC.
+
<pre><nowiki>
 +
$> python target.py nova folsom 2012.2.3 $(cat nova-bugs.txt)
 +
</nowiki></pre>
 +
 
 +
 
 +
=== Call For Testing ===
 +
 
 +
Call for testing, see [https://lists.launchpad.net/openstack/msg17332.html this example]
 +
 
 +
=== Tag ===
 +
 
 
# Push a commit to branch which does:<code><nowiki>FINAL = True</nowiki></code>
 
# Push a commit to branch which does:<code><nowiki>FINAL = True</nowiki></code>
 
# Tag the release:
 
# Tag the release:
 
<pre><nowiki>
 
<pre><nowiki>
−
$> git tag -s 2012.1.3
+
$> git tag -s 2012.2.3
−
$> git push gerrit tag 2012.1.3</nowiki></pre>
+
$> git push gerrit tag 2012.2.3</nowiki></pre>
 +
 
 +
 
 +
=== Close bugs ===
  
 
# Mark all [[FixCommitted]] bugs as [[FixReleased]]. With a small change:
 
# Mark all [[FixCommitted]] bugs as [[FixReleased]]. With a small change:
 
<pre><nowiki>
 
<pre><nowiki>
−
+series = proj.getSeries(name='essex')
+
+series = proj.getSeries(name='folsom')
 
+bugtasks = series.searchTasks(status='Fix Committed', omit_targeted=False)</nowiki></pre>
 
+bugtasks = series.searchTasks(status='Fix Committed', omit_targeted=False)</nowiki></pre>
 
  we can use <code><nowiki>process-fixcommitted-bugs.py</nowiki></code>:
 
  we can use <code><nowiki>process-fixcommitted-bugs.py</nowiki></code>:
 
<pre><nowiki>
 
<pre><nowiki>
−
$> python ./process-fixcommitted-bugs.py nova --onlymilestone 2012.1.3 --fixrelease
+
$> python ./process-fixcommitted-bugs.py nova --onlymilestone 2012.2.3 --fixrelease
 
</nowiki></pre>
 
</nowiki></pre>
 +
 +
 +
=== Upload The Release ===
  
 
# Upload the release:
 
# Upload the release:
 
<pre><nowiki>
 
<pre><nowiki>
−
$> ./upload_release.py nova 2012.1.3 20121012.13710</nowiki></pre>
+
$> ./upload_release.py nova 2012.1.3 20121012.13710
 +
</nowiki></pre>
 +
 
 +
 
 +
=== Docs ===
  
 
# Update [[SecurityAdvisories/Folsom]]
 
# Update [[SecurityAdvisories/Folsom]]
 
# Write release notes like [[ReleaseNotes/2012.1.3]]
 
# Write release notes like [[ReleaseNotes/2012.1.3]]
 
# Send release announcement like [https://lists.launchpad.net/openstack/msg17403.html this example].
 
# Send release announcement like [https://lists.launchpad.net/openstack/msg17403.html this example].
 +
# Update [[Releases]]
 +
 +
=== Rinse, Repeat ===
 +
 
# Open development for the next release by increasing the micro version in e.g. <code><nowiki>NOVA_VERSION</nowiki></code> and setting <code><nowiki>FINAL = False</nowiki></code>
 
# Open development for the next release by increasing the micro version in e.g. <code><nowiki>NOVA_VERSION</nowiki></code> and setting <code><nowiki>FINAL = False</nowiki></code>
 +
# Decide on date for next release, create milestones

Revision as of 16:22, 22 January 2013

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.

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.

Tarballs

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.

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.

Milestones

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

Bugs

  1. 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
  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 essex $(cat nova-bugs.txt)
  1. Target those bugs at the milestone 
$> python target.py nova folsom 2012.2.3 $(cat nova-bugs.txt)


Call For Testing

Call for testing, see this example

Tag

  1. Push a commit to branch which does:FINAL = True
  2. Tag the release:
$> git tag -s 2012.2.3
$> git push gerrit tag 2012.2.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

  1. Upload the release:
$> ./upload_release.py nova 2012.1.3 20121012.13710


Docs

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

Rinse, Repeat

  1. Open development for the next release by increasing the micro version in e.g. NOVA_VERSION and setting FINAL = False
  2. Decide on date for next release, create milestones
Retrieved from "https://wiki.openstack.org/w/index.php?title=StableBranchRelease&oldid=15198"