CEPH filesystem development
 help / color / mirror / Atom feed
From: Mark Nelson <mark.nelson@inktank.com>
To: Sage Weil <sweil@redhat.com>, ceph-devel@vger.kernel.org
Subject: Re: giant and hammer dates
Date: Tue, 29 Jul 2014 18:20:23 -0500	[thread overview]
Message-ID: <53D82C37.8020705@inktank.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1407291558060.26221@cobra.newdream.net>

On 07/29/2014 06:11 PM, Sage Weil wrote:
> We've talked a bit about moving to a ~4 month (instead of 3 month)
> cadence.  I'm still inclined in this direction because it means fewer
> stable releases that we will be maintaining and a longer and (hopefully)
> more productive interval to do real work in between.
>
> The other key point is that we don't want a repeat of the firefly delay.
> I think we should stay as close to a train model as we can.  If something
> isn't ready by freeze, let it wait for the next cycle.  We shouldn't be
> cramming things in at the end, especially big things.  As a general rule,
> big things should be merged early in the cycle so that we have lots of
> time to shake out the issues that only come out of lots of testing and
> aren't obvious from code review.
>
> Anyway, how about:
>
>            Freeze         Approx Release
>    Giant   Mon Sep  1     Mon Sep 29
>    Hammer  Mon Jan  4     Mon Feb  2
>
> That gives us another month for Giant, then September to shake out
> anything issues.  And then three full months before the Hammer freeze.
>
> What say ye?

6 months. ;)

> 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
>


  reply	other threads:[~2014-07-29 23:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-29 23:11 giant and hammer dates Sage Weil
2014-07-29 23:20 ` Mark Nelson [this message]
2014-07-30  4:59 ` Loic Dachary
2014-07-30 14:22   ` Sage Weil
2014-07-30 16:05     ` Loic Dachary
2014-07-30 14:22 ` Gregory Farnum
2014-07-30 16:15   ` Sage Weil
2014-08-02  8:17     ` Justin Erenkrantz
2014-07-30 16:52   ` Mark Nelson
2014-07-30 20:26     ` Eric Eastman

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=53D82C37.8020705@inktank.com \
    --to=mark.nelson@inktank.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=sweil@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