From: Loic Dachary <loic@dachary.org>
To: "Miyamae, Takeshi" <miyamae.takeshi@jp.fujitsu.com>
Cc: Ceph Development <ceph-devel@vger.kernel.org>,
"Shiozawa, Kensuke" <shiozawa.kennsu@jp.fujitsu.com>,
"Nakao, Takanori" <nakao.takanori@jp.fujitsu.com>
Subject: Re: Deadline of Github pull request for Hammer release (question)
Date: Fri, 23 Jan 2015 14:46:41 +0100 [thread overview]
Message-ID: <54C250C1.2010703@dachary.org> (raw)
In-Reply-To: <870DE8DBB716524BAE51B2D499EC81E40AA3F9AB@g01jpexmbyt24>
[-- Attachment #1: Type: text/plain, Size: 1593 bytes --]
Hi,
Note that you also need to update
https://github.com/dachary/ceph-erasure-code-corpus/blob/master/v0.85-764-gf3a1532/non-regression.sh
to include non regression tests for the most common cases of the SHEC plugin encoding / decoding. This is run by make check (this repository is a submodule of Ceph). It helps make sure that content encoded / decoded with a given version of the plugin can be encoded / decoded exactly in the same way by all future versions.
Cheers
On 06/01/2015 12:49, Miyamae, Takeshi wrote:
> Dear Loic,
>
> I'm Takeshi Miyamae, one of the authors of SHEC's blueprint.
>
> Shingled Erasure Code (SHEC)
> https://wiki.ceph.com/Planning/Blueprints/Hammer/Shingled_Erasure_Code_(SHEC)
>
> We have revised our blueprint shown in the last CDS to extend our erasure code
> layouts and describe the guideline for choosing SHEC among various EC plugins.
> We believe the blueprint now answers all the comments given at the CDS.
>
> In addition, we would like to ask for your advice on the schedule of our github
> pull request. More specifically, we would like to know its deadline for Hammer
> release.
> (As we have not really completed our verification of SHEC, we are wondering if
> we should make it open for early preview.)
>
> Thank you in advance,
> Takeshi Miyamae
>
> --
> 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-01-23 13:46 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-06 11:49 Deadline of Github pull request for Hammer release (question) Miyamae, Takeshi
2015-01-06 15:51 ` Loic Dachary
2015-01-13 10:24 ` Miyamae, Takeshi
2015-01-13 10:26 ` Loic Dachary
2015-01-13 10:34 ` Miyamae, Takeshi
2015-01-13 12:45 ` Loic Dachary
2015-01-13 17:05 ` Miyamae, Takeshi
2015-01-13 18:03 ` Loic Dachary
2015-01-20 0:48 ` Miyamae, Takeshi
2015-01-20 7:22 ` Loic Dachary
2015-01-20 9:07 ` Miyamae, Takeshi
2015-01-21 14:12 ` Loic Dachary
2015-01-22 8:42 ` Miyamae, Takeshi
2015-01-22 9:28 ` Loic Dachary
2015-01-22 16:34 ` Miyamae, Takeshi
2015-01-22 17:29 ` Loic Dachary
2015-01-23 1:16 ` Miyamae, Takeshi
2015-01-23 9:08 ` Loic Dachary
2015-01-23 12:47 ` Miyamae, Takeshi
2015-01-23 13:38 ` Loic Dachary
2015-01-24 15:52 ` Miyamae, Takeshi
2015-01-21 14:31 ` Loic Dachary
2015-01-23 13:46 ` Loic Dachary [this message]
2015-01-26 5:43 ` Miyamae, Takeshi
2015-01-26 11:02 ` Loic Dachary
2015-01-26 8:00 ` Miyamae, Takeshi
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=54C250C1.2010703@dachary.org \
--to=loic@dachary.org \
--cc=ceph-devel@vger.kernel.org \
--cc=miyamae.takeshi@jp.fujitsu.com \
--cc=nakao.takanori@jp.fujitsu.com \
--cc=shiozawa.kennsu@jp.fujitsu.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.