From: Loic Dachary <loic@dachary.org>
To: Yehuda Sadeh <yehuda@redhat.com>
Cc: Ceph Development <ceph-devel@vger.kernel.org>,
"Shu, Xinxin" <xinxin.shu@intel.com>
Subject: rgw and the next firefly release v0.80.10
Date: Fri, 22 May 2015 22:00:32 +0200 [thread overview]
Message-ID: <555F8AE0.6020001@dachary.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 742 bytes --]
Hi Yehuda,
The next firefly release as found at https://github.com/ceph/ceph/tree/firefly (68211f695941ee128eb9a7fd0d80b615c0ded6cf) passed the rgw suite (http://tracker.ceph.com/issues/11090#rgw). It includes https://github.com/ceph/ceph/pull/4697 which is the pull request backporting the fix for http://tracker.ceph.com/issues/11604 and http://tracker.ceph.com/issues/11622 to firefly.
Do you think it is ready for QE to start their own round of testing ?
Cheers
P.S. http://tracker.ceph.com/issues/11090#Release-information has direct links to the pull requests merged into firefly since v0.80.9 in case you need more context about one of them.
--
Loïc Dachary, Artisan Logiciel Libre
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next reply other threads:[~2015-05-22 20:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-22 20:00 Loic Dachary [this message]
2015-05-22 20:02 ` rgw and the next firefly release v0.80.10 Yehuda Sadeh-Weinraub
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=555F8AE0.6020001@dachary.org \
--to=loic@dachary.org \
--cc=ceph-devel@vger.kernel.org \
--cc=xinxin.shu@intel.com \
--cc=yehuda@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.