From: Loic Dachary <loic@dachary.org>
To: dillaman@redhat.com
Cc: Ceph Development <ceph-devel@vger.kernel.org>,
Abhishek Varshney <abhishek.varshney@flipkart.com>
Subject: Re: rbd and the next jewel release v10.2.3
Date: Tue, 23 Aug 2016 15:12:17 +0200 [thread overview]
Message-ID: <57BC4BB1.2090803@dachary.org> (raw)
In-Reply-To: <CA+aFP1CzY1UFgzUcWnCDAhqKH+p95gkhSZ7k+XhsuStm_y0ZnQ@mail.gmail.com>
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@dachary.org> 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
next prev parent reply other threads:[~2016-08-23 13:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-23 8:46 rbd and the next jewel release v10.2.3 Loic Dachary
2016-08-23 13:06 ` Jason Dillaman
2016-08-23 13:12 ` Loic Dachary [this message]
2016-08-23 13:32 ` Jason Dillaman
2016-08-23 13:32 ` Loic Dachary
2016-08-23 13:34 ` Loic Dachary
2016-08-23 13:35 ` Jason Dillaman
2016-08-24 7:07 ` Loic Dachary
2016-08-24 15:30 ` Jason Dillaman
2016-08-24 15:49 ` Loic Dachary
2016-08-24 17:40 ` Jason Dillaman
2016-08-24 20:09 ` Loic Dachary
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=57BC4BB1.2090803@dachary.org \
--to=loic@dachary.org \
--cc=abhishek.varshney@flipkart.com \
--cc=ceph-devel@vger.kernel.org \
--cc=dillaman@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.