Ceph » Stable releases

Approval from the leads of each component is before cutting a stable release.

• Send a mail to the lead including at least
  • the SHA of the commit from the stable branch to be published
  • the integration test results
• If approval is obtained from all leads, inform QE that it is ready for more tests and prepare the release notes
• If a lead asks for more issues to be backported, go back to preparing the release

To: Yehuda Sadeh <yehuda@redhat.com>
CC: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Firefly v0.80.10 backports (rgw)

Hi Yehuda,

A few issues related to rgw were backported to firefly[1]. They passed the rgw suite[2]. Do you think it is ready for QE to start their own round of testing ?

Cheers

[1] https://github.com/ceph/ceph/pulls?q=is%3Aopen+is%3Apr+milestone%3Afirefly+sort%3Aupdated-desc+label%3Argw
[2] http://tracker.ceph.com/issues/11090#rgw

-- Loïc Dachary, Artisan Logiciel Libre 

• Link the mail conversation archive with each lead from the issue tracking the progress of a given release, to make it easy to verify their approval later on. See hammer v0.94.2 as an example.