Tasks #17487
Updated by Nathan Cutler over 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":http://marc.info/?l=ceph-devel&m=147732037529059&w=2 ** Abhishek V. gets approval from all leads *** Yehuda, rgw "YES":http://marc.info/?t=147757781300007&r=1&w=2 *** John, CephFS "YES":http://marc.info/?l=ceph-devel&m=147757816802692&w=2 *** Jason, RBD "YES":http://marc.info/?t=147757689300003&r=1&w=2 *** Sam, rados "YES":http://marc.info/?l=ceph-devel&m=147758039103695&w=2 ** Abhishek L. writes and commits the release notes, including: *** <pre>Set require_jewel_osds osdmap flag on upgrade from hammer When the last hammer OSD in a cluster containing jewel MONs is upgraded to jewel, as of 10.2.4 the jewel MONs will issue this warning: "all OSDs are running jewel or later but the 'require_jewel_osds' osdmap flag is not set" and change the cluster health status to HEALTH_WARN. This is a signal for the admin to do "ceph osd set require_jewel_osds" - by doing this, the admin acknowledges that there is no downgrade path.</pre> notes ** Abhishek V. informs Yuri that the branch is ready for testing *DONE* ** Yuri runs additional integration tests *IN PROGRESS* ** 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: 427f357f0eed32c9ce17590ae9303a94e8b710e7 ** version: v10.2.4 ** type of release: point release ** where to publish the release: http://download.ceph.com/debian-jewel and http://download.ceph.com/rpm-jewel