From: Joao Eduardo Luis <joao@suse.de>
To: "Steffen W Sørensen" <stefws@me.com>, "Sage Weil" <sweil@redhat.com>
Cc: ceph-users@ceph.com, ceph-devel@vger.kernel.org
Subject: Re: [ceph-users] The first infernalis dev release will be v9.0.0
Date: Wed, 06 May 2015 09:29:05 +0100 [thread overview]
Message-ID: <5549D0D1.8020009@suse.de> (raw)
In-Reply-To: <5ABDA982-178E-4CD0-AF35-D79D064A5D49@me.com>
On 05/05/2015 08:54 PM, Steffen W Sørensen wrote:
>
>> On 05/05/2015, at 18.52, Sage Weil <sweil@redhat.com> wrote:
>>
>> On Tue, 5 May 2015, Tony Harris wrote:
>>> So with this, will even numbers then be LTS? Since 9.0.0 is following
>>> 0.94.x/Hammer, and every other release is normally LTS, I'm guessing 10.x.x,
>>> 12.x.x, etc. will be LTS...
>>
>> It looks that way now, although I can't promise the pattern will hold!
> I read it like major version is the release ie. Infernails, Jewel etc. following the letter position in the alfabet, I = 9th. letter, so we see all numbers 10,11,12,13…25
> minor numbers = 2 will denote LTS eg. <major release>.2.<patch level>
minor number '2' will denote 'stable', as oposed to 'dev' (minor = 0) or
'release candidate' (minor = 1). LTS has been every other major
version; so given Hammer is an LTS and Infernallis is not, then Jewel
would likely be a long term stable.
The point Tony was making is that this cadence, should it be kept as is,
would match perfectly with even major versions (jewel 10.x, L-release
12.x, ...).
-Joao
--
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
prev parent reply other threads:[~2015-05-06 8:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-04 16:09 The first infernalis dev release will be v9.0.0 Sage Weil
2015-05-04 17:18 ` Loic Dachary
[not found] ` <5547A9EB.4040404-cLsNCMjd+0JAfugRpC6u6w@public.gmane.org>
2015-05-04 17:21 ` Ken Dreyer
[not found] ` <alpine.DEB.2.00.1504301528410.5458-vIokxiIdD2AQNTJnQDzGJqxOck334EZe@public.gmane.org>
2015-05-05 14:20 ` Joao Eduardo Luis
[not found] ` <5548D1C0.30204-l3A5Bk7waGM@public.gmane.org>
2015-05-05 16:45 ` Sage Weil
[not found] ` <alpine.DEB.2.00.1505050945230.13336-vIokxiIdD2AQNTJnQDzGJqxOck334EZe@public.gmane.org>
2015-05-05 16:50 ` Tony Harris
2015-05-05 16:52 ` [ceph-users] " Sage Weil
[not found] ` <alpine.DEB.2.00.1505050951540.13336-vIokxiIdD2AQNTJnQDzGJqxOck334EZe@public.gmane.org>
2015-05-05 19:54 ` Steffen W Sørensen
2015-05-06 8:29 ` Joao Eduardo Luis [this message]
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=5549D0D1.8020009@suse.de \
--to=joao@suse.de \
--cc=ceph-devel@vger.kernel.org \
--cc=ceph-users@ceph.com \
--cc=stefws@me.com \
--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