CEPH filesystem development
 help / color / mirror / Atom feed
From: Loic Dachary <loic@dachary.org>
To: Josh Durgin <jdurgin@redhat.com>
Cc: Ceph Development <ceph-devel@vger.kernel.org>,
	Abhishek Varshney <abhishek.varshney@flipkart.com>
Subject: rbd and the next hammer release v0.94.4
Date: Fri, 02 Oct 2015 22:33:00 +0200	[thread overview]
Message-ID: <560EE9FC.2000402@dachary.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 523 bytes --]

Hi Josh,

The next hammer release as found at https://github.com/ceph/ceph/tree/hammer passed the rbd suite (http://tracker.ceph.com/issues/12701#note-61). Do you think the hammer branch is ready for QE to start their own round of testing ?

Cheers

P.S. http://tracker.ceph.com/issues/12701#Release-information has direct links to the pull requests merged into hammer since v0.94.3 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 --]

             reply	other threads:[~2015-10-02 20:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-02 20:33 Loic Dachary [this message]
2015-10-02 21:24 ` rbd and the next hammer release v0.94.4 Josh Durgin

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=560EE9FC.2000402@dachary.org \
    --to=loic@dachary.org \
    --cc=abhishek.varshney@flipkart.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=jdurgin@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox