Ceph » Stable releases

Create a new version¶

*

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 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)

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 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

• Preparing the release
• Cutting the 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

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