From: Loic Dachary <loic@dachary.org>
To: Robert LeBlanc <robert@leblancnet.us>
Cc: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: What should be in the next hammer/firefly release ?
Date: Fri, 18 Sep 2015 08:57:19 +0200 [thread overview]
Message-ID: <55FBB5CF.30206@dachary.org> (raw)
In-Reply-To: <CAANLjFo8Knp1OHy69fnxxtDE0WKzZkmk3U3yCPpW16pxtaKDtQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2633 bytes --]
Hi Robert,
http://tracker.ceph.com/issues/10399 was backported to hammer and will be in v0.94.4 (see http://tracker.ceph.com/issues/12751 for details).
Cheers
On 18/09/2015 02:44, Robert LeBlanc wrote:
> Can we get http://tracker.ceph.com/issues/10399 into hammer. We hit this today.
> ----------------
> Robert LeBlanc
> PGP Fingerprint 79A2 9CA4 6CC4 45DD A904 C70E E654 3BB2 FA62 B9F1
>
>
> On Thu, Sep 10, 2015 at 4:57 AM, Miyamae, Takeshi wrote:
>> Hi Loic,
>
>> As the last pull request #5257 was committed into the main trunk,
>> we believe all the SHEC codes in main trunk are ready to be backported into Hammer branch.
>> What can we do at this moment?
>
>> Best regards,
>> Takeshi Miyamae
>
>> -----Original Message-----
>> From: Miyamae, Takeshi/宮前 剛
>> Sent: Thursday, September 3, 2015 4:09 PM
>> To: 'ceph-devel-owner@vger.kernel.org'
>> Cc: Paul Von-Stamwitz (PVonStamwitz@us.fujitsu.com); Toshine, Naoyoshi/利根 直佳; Shiozawa, Kensuke/塩沢 賢輔; Nakao, Takanori/中尾 鷹詔 (nakao.takanori@jp.fujitsu.com)
>> Subject: Re: What should be in the next hammer/firefly release ?
>
>> Dear Loic,
>
>> We would like to let following two patches be backported to hammer v0.94.4.
>> (And our wish is finally backporting these patches to RHCS v1.3.) Can it be possible? If possible, please let us know what should be started at first.
>> (Caution: #5257 has not been committed to master branch yet.)
>
>> erasure-code: shec plugin feature #5493
>> https://github.com/ceph/ceph/pull/5493
>
>> erasure code: shec performance optimization by decoding cache #5257
>> https://github.com/ceph/ceph/pull/5257
>
>> Best regards,
>> Takeshi Miyamae
>
>> -----Original Message-----
>> From: Loic Dachary dachary.org>
>> Subject: What should be in the next hammer/firefly release ?
>> Newsgroups: gmane.comp.file-systems.ceph.devel
>> Date: 2015-09-02 11:00:53 GMT (15 hours and 32 minutes ago) Hi,
>
>> I added a link to
>
>> http://tracker.ceph.com/projects/ceph-releases/wiki/HOWTO#Overview-of-the-backports-in-progress
>
>> to show all issues that should be in the next point release for
>
>> hammer v0.94.4 : http://tracker.ceph.com/versions/495
>> firefly v0.80.11 : http://tracker.ceph.com/versions/480
>
>> Cheers
>
>> --
>> Loïc Dachary, Artisan Logiciel Libre
>
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
Loïc Dachary, Artisan Logiciel Libre
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2015-09-18 6:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-10 10:57 Re: What should be in the next hammer/firefly release ? Miyamae, Takeshi
2015-09-10 11:12 ` Loic Dachary
2015-09-16 10:37 ` Miyamae, Takeshi
2015-09-18 0:44 ` Robert LeBlanc
2015-09-18 6:57 ` Loic Dachary [this message]
2015-09-18 16:10 ` Robert LeBlanc
-- strict thread matches above, loose matches on Subject: below --
2015-09-02 11:00 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=55FBB5CF.30206@dachary.org \
--to=loic@dachary.org \
--cc=ceph-devel@vger.kernel.org \
--cc=robert@leblancnet.us \
/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.