Ceph » Stable releases

h3. Create a new version

* 

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 **Release** field to the release (for instance **firefly**)

* Set the **Target version** field to the version (for instance **firefly v0.80.10**)

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 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 with severity Critical, the relase 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. Release information

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

* version: v0.80.10

* type of release: point release

* where to publish the release: debian/rpm-$release