Ceph » Stable releases

Workflow¶

• Preparing the release
• Cutting the release
  • Nathan asks Abhishek L. if a point release should be published - YES
  • Nathan gets approval from all leads
    • Yehuda, RGW - SKIPPED
    • John, CephFS - YES
    • Jason, RBD - SKIPPED
    • Josh, RADOS - SKIPPED
  • Abhishek L. writes and commits the release notes - https://github.com/ceph/ceph/pull/16318
  • Nathan informs Yuri that the branch is ready for testing - DONE
  • Yuri runs additional integration tests - DONE
  • 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 - DONE
  • Alfredo creates the packages and sets the release tag - DONE
  • Abhishek posts release announcement on https://ceph.com/community/blog - http://ceph.com/community/v10-2-9-jewel-released/ DONE
  • Nathan updates upgrade/jewel-x/point-to-point-x to do 10.2.0 -> 10.2.9 -> x - SKIPPED
  • Nathan sends release announcement to public mailing lists

Release information¶

• branch to build from: jewel, commit: 9295f588535c45431d19b9601b4063c8de88752d
• version: v10.2.9
• type of release: point release
• where to publish the release: http://download.ceph.com/debian-jewel and http://download.ceph.com/rpm-jewel