Ceph » Stable releases

h3. Create a new version

* http://tracker.ceph.com/projects/ceph/versions/new

* only set the name with **release version** (for instance **v0.80.10**)

* select *Shared with subprojects*

h3. Decide who will drive the point release

There is no formal process. Someone volunteers and discuss it with [[HOWTO#Whos-who|other members of the team]], via e-mail or irc.

h3. Create new task

* http://tracker.ceph.com/projects/ceph-releases/issues/new

* Title *release version* (for instance **firefly v0.80.10**)

* Assign it to the "backporter":http://tracker.ceph.com/projects/ceph-releases responsible for it

* Set the *Affected Versions* field to the version (for instance **v0.80.10**)

* Set the priority to *Urgent* for releases that contain only a few backports that need to be published immediately and *High* otherwise

* Update the [[HOWTO|HOWTO landing page]] (link to the task and the "Who's who section")

h3. Add a workflow section to the description

The issue is used to figure out at what point of the release workflow it currently is. The "development workflow":http://ceph.com/docs/master/dev/development-workflow/ must be copied and edited to reflect the specifics of the version being released (i.e. replacing roles by names of people responsible for a given component at this point in time for instance). Here is an example from "firefly v0.80.10":http://tracker.ceph.com/issues/11090

* "Preparing the release":http://ceph.com/docs/master/dev/development-workflow/#preparing-a-new-release

* "Cutting the release":http://ceph.com/docs/master/dev/development-workflow/#cutting-a-new-stable-release

** Loic asks Sage if a point release should be published

** Loic gets approval from all leads

*** Yehuda, rgw: 

*** Gregory, CephFS:

*** Josh, RBD:

*** Sam, rados:

** Sage writes and commits the release notes 

** Loic informs Yuri that the branch is ready for testing 

** Yuri runs additional integration tests

** If Yuri discovers new bugs that need to be backported urgently (i.e. their priority is set to *Urgent*), the release goes back to being prepared, it was not ready after all

** Yuri informs Alfredo that the branch is ready for release

** Alfredo creates the packages and sets the release tag

h3. Add a release information template to the description

This will be used by the person responsible for the publishing the release. Although it is largely redundant with information from the context, it can convenientely be copy pasted and does not require any understanding of the conventions used for backporting. The release manager can publish the release with just this information and nothing else. The commit hash (**???**) below is in the release branch and has "received approval by everyone involved":http://ceph.com/docs/master/dev/development-workflow/#cutting-a-new-stable-release

* branch to build from: firefly, commit:???

* version: v0.80.10

* type of release: point release

* where to publish the release: http://download.ceph.com/debian-$release and http://download.ceph.com/rpm-$release