From: Loic Dachary <loic@dachary.org>
To: Sage Weil <sage@inktank.com>, ceph-devel@vger.kernel.org
Subject: Re: firefly timing
Date: Mon, 03 Feb 2014 18:29:20 +0100 [thread overview]
Message-ID: <52EFD1F0.1050808@dachary.org> (raw)
In-Reply-To: <alpine.DEB.2.00.1402030819030.6345@cobra.newdream.net>
[-- Attachment #1: Type: text/plain, Size: 2087 bytes --]
Hi Sage,
I'm both happy and stressed out to have more time to work on erasure code :-) If I'm not mistaken, the Firefly freeze is now set to Friday 14th, 2014. During this time I plan to focus on implementing whatever is required for Erasure Code to work with the default jerasure plugin ( I'm thinking https://github.com/ceph/ceph/pull/1144 , https://github.com/ceph/ceph/pull/1177 etc. ). If there is enough time, it would also be nice to have the pyramid plugin https://github.com/ceph/ceph/pull/1142 merged in, but this is not mandatory.
Is there a better use of my time during this sprint ?
Cheers
On 03/02/2014 17:21, Sage Weil wrote:
> The original firefly freeze date was Jan 17, but I added another sprint
> because there were several things that weren't quite ready yet (the cache
> tier code and erasure coding). Two weeks later we are much closer, but
> the EC functionality still needs a bit more time. I would like to push
> out the freeze by one more sprint so that all of the code can land. In
> particular, I would rather use the next sprint to get EC ready and shift
> other development focus to stability early, instead of pulling last-minute
> stuff in after the freeze date.
>
> This bends/breaks the 'train model' schedule we are aiming for, but my
> assumption is that people are more interested in seeing the new
> functionality in place than in the exact timing.
>
> The only time dependency that I am aware of is the looming 14.04 freeze
> date. I'm hoping that we can (worst case) put an -rc release in place and
> update as the code stabilizes over the next several weeks. James, will
> this be problematic?
>
> Does anybody else have questions or concerns about adding in another
> sprint before we freeze for firefly?
>
> Thanks-
> sage
>
> --
> 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: 263 bytes --]
next prev parent reply other threads:[~2014-02-03 17:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-03 16:21 firefly timing Sage Weil
2014-02-03 17:29 ` Loic Dachary [this message]
2014-02-04 6:14 ` James Page
2014-02-04 6:20 ` Sage Weil
2014-02-04 6:33 ` James Page
-- strict thread matches above, loose matches on Subject: below --
2014-03-18 4:45 Sage Weil
[not found] ` <alpine.DEB.2.00.1403172115140.24236-vIokxiIdD2AQNTJnQDzGJqxOck334EZe@public.gmane.org>
2014-03-18 7:07 ` Stefan Priebe - Profihost AG
[not found] ` <5327F0A7.8010105-2Lf/h1ldwEHR5kwTpVNS9A@public.gmane.org>
2014-03-18 7:13 ` Ирек Фасихов
[not found] ` <CAF-rypyVjvuddtaj=cW_yJowzGzCq0m7LgW6S=2zK1aAvsfrTA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-03-18 7:54 ` Karan Singh
2014-03-18 10:00 ` Alexandre DERUMIER
2014-03-18 16:06 ` Sage Weil
[not found] ` <alpine.DEB.2.00.1403180905500.316-vIokxiIdD2AQNTJnQDzGJqxOck334EZe@public.gmane.org>
2014-03-18 16:20 ` Stefan Priebe - Profihost AG
2014-03-18 16:38 ` Milosz Tanski
[not found] ` <CANP1eJEDccw7doegUSoNKceQUgoNOfpHW1_y1Oz1fk54WDdb4w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-03-18 17:17 ` Sage Weil
[not found] ` <alpine.DEB.2.00.1403181014410.5823-vIokxiIdD2AQNTJnQDzGJqxOck334EZe@public.gmane.org>
2014-03-18 20:12 ` Sage Weil
2014-03-18 22:32 ` Milosz Tanski
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=52EFD1F0.1050808@dachary.org \
--to=loic@dachary.org \
--cc=ceph-devel@vger.kernel.org \
--cc=sage@inktank.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.