From: Wido den Hollander <wido@42on.com>
To: Patrick McGarry <patrick@inktank.com>
Cc: Ceph Devel <ceph-devel@vger.kernel.org>
Subject: Re: Release Cadence
Date: Wed, 13 Mar 2013 12:08:20 +0100 [thread overview]
Message-ID: <51405E24.9030702@42on.com> (raw)
In-Reply-To: <CAP8Oy=LhkgGeUe8KLHJtbKwmsJe3-0idApOzx9kTsBm67fgEFA@mail.gmail.com>
On 03/12/2013 09:12 PM, Patrick McGarry wrote:
> Hey all,
>
> Just wanted to link to a few words on the new Ceph release cadence.
>
> http://ceph.com/community/ceph-settles-in-to-aggressive-release-cadence/
>
> Feel free to hit us with any questions. Thanks.
>
>
One note in the LTS releases. While LTS releases would be great, I agree
that at this point in time Ceph isn't ready for it.
Point being that the API changes and such are becoming less frequent,
but think about the burden of having to facilitate an upgrade path from
code which was written one year ago to the current point in time.
Think about the new monitor proposal and such.
Just to conclude, I think it's wise for now to not call anything "LTS"
yet. I however fully agree that in the longer run it would be desirable
for production deployments.
>
> Best Regards,
>
> --
> Patrick McGarry
> Director, Community
> Inktank
>
> http://ceph.com || http://inktank.com
> @scuttlemonkey || @ceph || @inktank
> --
> 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
>
--
Wido den Hollander
42on B.V.
Phone: +31 (0)20 700 9902
Skype: contact42on
next prev parent reply other threads:[~2013-03-13 11:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-12 20:12 Release Cadence Patrick McGarry
2013-03-13 11:08 ` Wido den Hollander [this message]
2013-03-13 11:41 ` Wolfgang Hennerbichler
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=51405E24.9030702@42on.com \
--to=wido@42on.com \
--cc=ceph-devel@vger.kernel.org \
--cc=patrick@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.