Jump to: navigation, search

Difference between revisions of "ReleaseTeam/How To Release"

(Updates at grizzly-3)
(Updated for new tools)
Line 1: Line 1:
 
__NOTOC__
 
__NOTOC__
 
Raw notes for release monkeys in case I end up under a bus.
 
Raw notes for release monkeys in case I end up under a bus.
 +
 +
All tools mentioned here can be grabbed from this [https://github.com/ttx/openstack-releasing github repo].
  
 
= Milestone publication =
 
= Milestone publication =
  
Supposing release under development is "Morlock" (2014.1) and we want to publish "morlock-2" milestone.
+
<pre><nowiki>
 +
PROJECT=nova
 +
VERSION=2013.1
 +
MILESTONE=grizzly-3
 +
SHORT=g3
 +
</nowiki></pre>
  
 
=== Pre-flight checks ===
 
=== Pre-flight checks ===
Line 11: Line 18:
  
 
<pre><nowiki>
 
<pre><nowiki>
cd project
+
./repo_tarball_diff.sh $PROJECT master
tarball-repo-diff
 
 
</nowiki></pre>
 
</nowiki></pre>
 
  
 
==== Tarball/version status ====
 
==== Tarball/version status ====
* Check that the *-tarball jenkins jobs work properly and that they produce the right version numbers
+
* Check that the $PROJECT-[branch-]tarball jenkins jobs work properly and that they produce the right version numbers
  
 
==== Check bugs ====
 
==== Check bugs ====
Line 38: Line 43:
  
 
<pre><nowiki>
 
<pre><nowiki>
./process-fixcommitted-bugs.py nova --milestone morlock-2 --settarget morlock-2 --fixrelease
+
./process_bugs.py $PROJECT --settarget=$MILESTONE --fixrelease
 
</nowiki></pre>
 
</nowiki></pre>
 
  
 
==== Wait for tarball build ====
 
==== Wait for tarball build ====
* Wait for the *-branch-tarball job run to generate a PROJ-milestone-proposed.tar.gz
+
* Wait for the $PROJECT-branch-tarball job run to generate a $PROJECT-milestone-proposed.tar.gz
  
 
==== Announce candidate builds (once all done) ====
 
==== Announce candidate builds (once all done) ====
Line 52: Line 56:
  
 
==== Track milestone-critical fixes ====
 
==== Track milestone-critical fixes ====
* Target milestone-critical fixes to morlock-2
+
* Target milestone-critical fixes to $MILESTONE
 
* Backport them to milestone-proposed (see [[GerritJenkinsGithub#Authoring_Changes_for_milestone-proposed|how to do it]])
 
* Backport them to milestone-proposed (see [[GerritJenkinsGithub#Authoring_Changes_for_milestone-proposed|how to do it]])
  
Line 65: Line 69:
 
git checkout milestone-proposed
 
git checkout milestone-proposed
 
git pull
 
git pull
git tag -s "2014.1.m2"
+
git tag -s "$PROJECT.$SHORT"
 
git push --tags gerrit
 
git push --tags gerrit
 
</nowiki></pre>
 
</nowiki></pre>
  
 
==== Wait for tarball build ====
 
==== Wait for tarball build ====
* Wait for the *-tarball job run to generate a PROJ-2014.1.m2.tar.gz
+
* Wait for the $PROJECT-tarball job run to generate a $PROJECT-$VERSION.$SHORT.tar.gz
  
 
==== Upload milestone ====
 
==== Upload milestone ====
  
 
<pre><nowiki>
 
<pre><nowiki>
upload_release.py nova 2014.1 --milestone=morlock-2
+
./upload_release.py $PROJECT $VERSION --milestone=$MILESTONE
 
</nowiki></pre>
 
</nowiki></pre>
 
  
 
==== Announce milestone ====
 
==== Announce milestone ====

Revision as of 14:42, 11 March 2013

Raw notes for release monkeys in case I end up under a bus.

All tools mentioned here can be grabbed from this github repo.

Milestone publication

PROJECT=nova
VERSION=2013.1
MILESTONE=grizzly-3
SHORT=g3

Pre-flight checks

Missing files check

./repo_tarball_diff.sh $PROJECT master

Tarball/version status

  • Check that the $PROJECT-[branch-]tarball jenkins jobs work properly and that they produce the right version numbers

Check bugs

  • Look at the list of FixCommitted bugs, sanity-check that they were fixed during the period

Get PTL signoff

  • Note down MP cut commit id

MP cut (Tuesday)

Deferring blueprints

  • Move all incomplete blueprints to the next milestone
  • Move all non-milestone-critical bugs to the next milestone

Create MP branch from previous commit

  • Use review.openstack.org admin panel to create branch
  • Branch name is "milestone-proposed", initial revision is the MP cut commit id (or HEAD)

Process FixCommitted bugs

./process_bugs.py $PROJECT --settarget=$MILESTONE --fixrelease

Wait for tarball build

  • Wait for the $PROJECT-branch-tarball job run to generate a $PROJECT-milestone-proposed.tar.gz

Announce candidate builds (once all done)

  • Email to openstack general ML
  • Twitter

In the next days (Wednesday-Thursday)

Track milestone-critical fixes

  • Target milestone-critical fixes to $MILESTONE
  • Backport them to milestone-proposed (see how to do it)

Get PTL signoff

  • Note down milestone cut commit id

Milestone publication (Thursday)

Push tag to MP

git checkout milestone-proposed
git pull
git tag -s "$PROJECT.$SHORT"
git push --tags gerrit

Wait for tarball build

  • Wait for the $PROJECT-tarball job run to generate a $PROJECT-$VERSION.$SHORT.tar.gz

Upload milestone

./upload_release.py $PROJECT $VERSION --milestone=$MILESTONE

Announce milestone

  • Email to openstack general ML
  • Twitter

Post-milestone

Remove milestone-proposed branches

  • In review.openstack.org project branch admin panel

Final release (outdated !)

Supposing we want to release "Morlock" (2014.1), and next release is called "Night" (2014.2).

Pre-flight checks

Create next series

  • Create "night" series in Launchpad
  • Set status to Future, Set release manager

Missing files check

cd project
tarball-repo-diff

Tarball/version status

  • Check that the *-tarball jenkins jobs work properly and that they produce the right version numbers

Check bugs

  • Look at the list of FixCommitted bugs, sanity-check that they were fixed during the period

MP cut (switch master to next version)

Get PTL signoff

  • This should be done close to the RC1 cut
  • Note down MP cut commit id

Bump master milestone code

  • Use common-bump-milestone Jenkins job
  • Select project, "master" and type "n1"

Push new version to master as first commit

  • /!\ This needs to be done as the very first commit after the n1 milestone bump !
  • Prepare change which sets next version on master branch
  • Get it approved by core and make sure it's merged

Create MP branch from previous commit

  • Use review.openstack.org admin panel to create branch
  • Branch name is "milestone-proposed", initial revision is the MP cut commit id

Process FixCommitted bugs

./process-fixcommitted-bugs.py nova --milestone morlock-rc1 --settarget morlock-rc1 --fixrelease

RC1 cut

Get PTL signoff

  • Check that the branch contents are ready to go from PTL perspective

Push FINAL=True commit to MP (some projects only)

  • Prepare change which sets FINAL=True on milestone-proposed branch
  • Approve and make sure it's merged

Wait for Final tarball

  • Wait for the *-tarball job run
  • Note down tarball version

Bump MP milestone code to rc2

  • Use common-bump-milestone Jenkins job
  • Select project, "milestone-proposed" and type "rc2"

Push rc1 tag to MP

git checkout milestone-proposed
git pull
git tag -s morlock-rc1
git push --tags gerrit

Upload release

upload_release.py nova 2014.1 --milestone=morlock-rc1

Announce RC1

  • Email to openstack general ML
  • Twitter

Further RC-X windows

Decision to open next RC window

  • Consider m-rc-potential bugs and discuss with PTL if they warrant a respin

Create RC-X milestone page

  • Create the RC-X milestone page on Launchpad
  • Target relevant bugs

Refine/fix bugs

  • Track bug fixes
  • Facilitate backports

Get candidate tarball

  • Wait for the *-tarball job run
  • Note down tarball version

Get PTL signoff

  • Get confirmation that RC is releasable from PTL

Bump MP milestone code to next rcX+1

  • Use common-bump-milestone Jenkins job
  • Select project, "milestone-proposed" and type "rcX+1"

Push M-rcX tag to MP

git checkout milestone-proposed
git pull
git tag -s morlock-rcX
git push --tags gerrit

Upload release

upload_release.py nova 2014.1 --milestone=morlock-rcX

Announce RC-X

Final release

Create final release milestone page

  • Create the 2014.1 final milestone page on Launchpad

Push all bugs and blueprints to final page

consolidate_release_page.py nova morlock 2014.1

This can take a very long time. For large bugs you will have to run it multiple times. Verify all intermediary milestone pages are now empty.

Push final version tag to MP

git checkout milestone-proposed
git pull
git tag -s 2014.1
git push --tags gerrit

Promote last RC to release

promote_rc.py PROJECT 2014.1 rc2

Add release notes link to release page

Announce release

  • openstack-announce, openstack general ML
  • Twitter etc.

Post-release

Update "Releases" wiki page

Switch dev focus

  • Switch dev focus to N and N status to under active development
  • Switch M to current stable release, set release manager = openstack-stable-maint
  • Switch M-1 to Obsolete

Clean rc-potential tags

Create devnull branch (from MP)

  • Go to review.openstack.org project branch admin panel
  • New branch: "devnull", Initial revision: "milestone-proposed"

Push .1 version to devnull branch

git checkout -t -b devnull origin/devnull
vi nova/version.py # set to 2014.1.1
git commit -a
git review devnull

Create stable/folsom branch from devnull branch

  • Go to review.openstack.org project branch admin panel
  • New branch: "stable/morlock", Initial revision: "devnull"

Remove devnull and milestone-proposed branches

  • In review.openstack.org project branch admin panel

Bump MP milestone code

  • Use common-bump-milestone Jenkins job
  • Select project, "milestone-proposed" and type "n1"

Swift releases (outdated !)

Swift uses separate versioning and does not use milestones. Let's suppose we are releasing 1.8.2 and next version is called 1.8.3.

Pre-flight checks

Missing files check

cd swift
tarball-repo-diff


Tarball/version status

  • Check that the swift-tarball jenkins jobs work properly and that they produce the right version numbers

Check bugs & blueprints

  • Look at the list of FixCommitted bugs, sanity-check that they were fixed during the period
  • Check that the 1.8.2 milestone page is sane (all implemented blueprints)

Get PTL signoff

  • Check that the 1.8.2 changelog was committed to master
  • Note down MP cut commit id

MP cut

Push new version to master

  • Prepare change which sets 1.8.3 on master branch
  • Get it approved by swift-core and make sure it's merged

Create MP branch from previous commit

  • Use review.openstack.org admin panel to create branch
  • Branch name is "milestone-proposed", initial revision is the MP cut commit id

Process FixCommitted bugs

./process-fixcommitted-bugs.py swift --milestone 1.8.2 --settarget 1.8.2 --fixrelease


Wait for tarball build

  • Wait for the swift-tarball job run
  • Note down tarball version

QA for proposed release

Push FINAL=True commit to MP

  • Prepare change which sets FINAL=True on milestone-proposed branch
  • Approve and make sure it's merged

Get Final PTL signoff

  • Note down release commit id

Wait for tarball build

  • Wait for the swift-tarball job run
  • Note down tarball version

Release publication

Push tag to MP

git checkout milestone-proposed
git pull
git tag -s 1.8.2
git push --tags gerrit


Upload milestone

upload_release.py swift 1.8.2


Announce release

  • Email to openstack general, openstack-announce ML
  • Twitter

Post-milestone

Remove milestone-proposed branch

  • In review.openstack.org project branch admin panel