From: Loic Dachary <loic@dachary.org>
To: Samuel Just <sjust@redhat.com>
Cc: Ceph Development <ceph-devel@vger.kernel.org>,
Abhishek Varshney <abhishek.varshney@flipkart.com>
Subject: Re: rados and the next jewel release v10.2.3
Date: Mon, 29 Aug 2016 17:00:37 +0200 [thread overview]
Message-ID: <57C44E15.3030304@dachary.org> (raw)
In-Reply-To: <57BF0798.5060302@dachary.org>
For the record, Kefu said today that in his opinion no important backports are missing at the moment
On 25/08/2016 16:58, Loic Dachary wrote:
> For the record, you agreed today that nothing is missing according to you. But you advised to ask Kefu's input.
>
> On 23/08/2016 10:56, Loic Dachary wrote:
>> Hi Sam,
>>
>> The next jewel release as found at https://github.com/ceph/ceph/tree/jewel passed the rados suite (http://tracker.ceph.com/issues/16344#note-26 except for one known bug http://tracker.ceph.com/issues/16516). Do you think the jewel branch is ready for QE to start their own round of testing ?
>>
>> Cheers
>>
>
--
Loïc Dachary, Artisan Logiciel Libre
prev parent reply other threads:[~2016-08-29 15:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-23 8:56 rados and the next jewel release v10.2.3 Loic Dachary
2016-08-25 14:58 ` Loic Dachary
2016-08-29 15:00 ` Loic Dachary [this message]
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=57C44E15.3030304@dachary.org \
--to=loic@dachary.org \
--cc=abhishek.varshney@flipkart.com \
--cc=ceph-devel@vger.kernel.org \
--cc=sjust@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.