From: Danny Al-Gaaf <danny.al-gaaf@bisect.de>
To: Sage Weil <sage@newdream.net>, ceph-devel@vger.kernel.org
Subject: Re: v0.93 Hammer release candidate released
Date: Sun, 01 Mar 2015 23:04:49 +0100 [thread overview]
Message-ID: <54F38D01.6070200@bisect.de> (raw)
In-Reply-To: <alpine.DEB.2.00.1502271408230.1577@cobra.newdream.net>
Am 27.02.2015 um 23:10 schrieb Sage Weil:
> This is the first release candidate for Hammer, and includes all
> of the features that will be present in the final release. We
> welcome and encourage any and all testing in non-production
> clusters to identify any problems with functionality, stability, or
> performance before the final Hammer release.
>
> We suggest some caution in one area: librbd. There is a lot of
> new functionality around object maps and locking that is disabled
> by default but may still affect stability for existing images. We
> are continuing to shake out those bugs so that the final Hammer
> release (probably v0.94) will be stable.
I've opened bug #10981. This one should get fixed for Hammer GM since
the core code of ceph shouldn't throw any -Wdeprecated-declarations
warnings during compilation.
Danny
next prev parent reply other threads:[~2015-03-01 22:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-27 22:10 v0.93 Hammer release candidate released Sage Weil
2015-03-01 22:04 ` Danny Al-Gaaf [this message]
[not found] ` <alpine.DEB.2.00.1502271408230.1577-vIokxiIdD2AQNTJnQDzGJqxOck334EZe@public.gmane.org>
2015-03-03 5:16 ` Sage Weil
[not found] ` <alpine.DEB.2.00.1503022114370.25972-vIokxiIdD2AQNTJnQDzGJqxOck334EZe@public.gmane.org>
2015-03-03 5:18 ` [ceph-users] " Sage Weil
2015-03-04 9:36 ` Thomas Lemarchand
2015-03-04 17:02 ` [ceph-users] " Sage Weil
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=54F38D01.6070200@bisect.de \
--to=danny.al-gaaf@bisect.de \
--cc=ceph-devel@vger.kernel.org \
--cc=sage@newdream.net \
/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.