The jewel-backport branch also has all the pull request you mentionned below. The details of what it contains are at http://tracker.ceph.com/issues/16344#note-32 On 23/08/2016 15:32, Loic Dachary wrote: > The jewel-backport branch is in gitbuilder with the http://tracker.ceph.com/issues/16950 backport https://github.com/ceph/ceph/pull/10827 . I'll wait to hear from you before scheduling a run however. > > On 23/08/2016 15:12, Loic Dachary wrote: >> Ok. Let me know when the backport of http://tracker.ceph.com/issues/16950 is ready and I'll schedule tests. If you'd rather do the test yourself, that's also fine with me :-) >> >> Cheers >> >> On 23/08/2016 15:06, Jason Dillaman wrote: >>> If at all possible, I would definitely like to see the following >>> included in 10.2.3 since users are hitting it in the field: >>> >>> http://tracker.ceph.com/issues/16950 >>> >>> ... and given that would require another RBD test run prior to merge, >>> I would also like to include the following which already have open >>> PRs: >>> >>> https://github.com/ceph/ceph/pull/10791 >>> https://github.com/ceph/ceph/pull/10790 >>> https://github.com/ceph/ceph/pull/10792 >>> https://github.com/ceph/ceph/pull/10646 >>> https://github.com/ceph/ceph/pull/10647 >>> https://github.com/ceph/ceph/pull/10786 >>> >>> I can create a PR for the high priority issue this morning. >>> >>> On Tue, Aug 23, 2016 at 4:46 AM, Loic Dachary <loic@xxxxxxxxxxx> wrote: >>>> Hi Jason, >>>> >>>> The next jewel release as found at https://github.com/ceph/ceph/tree/jewel received (I think :-) enough rbd backports to cut the release. It was more challenging than usual and I'd like to thank you and Mykola for helping with the tricky parts. >>>> >>>> Do you think the jewel branch is ready for QE to start their own round of testing ? >>>> >>>> Cheers >>>> >>>> -- >>>> Loïc Dachary, Artisan Logiciel Libre >>>> >>> >>> >>> >> > -- Loïc Dachary, Artisan Logiciel Libre -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
