Tasks #17851
Updated by Nathan Cutler about 7 years ago
h3. Workflow * "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 ** Abhishek V. asks Abhishek L. if a point release should be published - YES ** Abhishek V. gets approval from all leads *** Yehuda, rgw - YES (February 20, 2017 on ceph-devel mailing list) *** John, CephFS - YES (February 22, 2017 on ceph-devel mailing list) *** Jason, RBD - YES (February 20, 2017 on ceph-devel mailing list) *** Josh, rados - YES (February 21, 2017 on ceph-devel mailing list) ** Abhishek L. writes and commits the release notes ** Abhishek V. informs Yuri that the branch is ready for testing - DONE (February 22, 2017 on ceph-devel mailing list) ** 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. Release information ** branch to build from: jewel, commit: ecdfb7ce0c29aa5eb954b3644e5be1544e018515 TBD ** version: v10.2.6 ** type of release: point release ** where to publish the release: http://download.ceph.com/debian-jewel and http://download.ceph.com/rpm-jewel