All of lore.kernel.org
 help / color / mirror / Atom feed
From: Loic Dachary <loic@dachary.org>
To: Sage Weil <sweil@redhat.com>,
	ceph-devel@vger.kernel.org, ceph-users@ceph.com
Subject: Re: The first infernalis dev release will be v9.0.0
Date: Mon, 04 May 2015 19:18:35 +0200	[thread overview]
Message-ID: <5547A9EB.4040404@dachary.org> (raw)
In-Reply-To: <alpine.DEB.2.00.1504301528410.5458@cobra.newdream.net>

[-- Attachment #1: Type: text/plain, Size: 1743 bytes --]

+1 ;-)

On 04/05/2015 18:09, Sage Weil wrote:
> The first Ceph release back in Jan of 2008 was 0.1.  That made sense at 
> the time.  We haven't revised the versioning scheme since then, however, 
> and are now at 0.94.1 (first Hammer point release).  To avoid reaching 
> 0.99 (and 0.100 or 1.00?) we have a new strategy.  This was discussed a 
> bit on ceph-devel and in #ceph-devel and there doesn't appear to be any 
> scheme that everyone likes.
> 
> So, we're going to go with something that only a few people dislike:
> 
>  x.0.z - development releases (for early testers and the brave at heart)
>  x.1.z - release candidates (for test clusters, brave users)
>  x.2.z - stable/bugfix releases (for users)
> 
> x will start at 9 for Infernalis ("I" is the 9th letter), making our first 
> development release of the 9th release cycle 9.0.0.  Subsequent 
> development releases will be 9.0.1, 9.0.2, etc.
> 
> In a couple months we'll have a 9.1.0 (and maybe 9.1.1) release candidate.
> 
> A few weeks after that we'll have the Infernalis release 9.2.0, followed 
> by stable bug fix updates 9.2.1, 9.2.2, etc., and then begin work on the 
> Jewel (10.y.z) release.
> 
> We'll see how this works out.  We can adjust this in the future to any 
> other 9.y.z scheme (e.g., 9.1, 9.2 etc dev releases and 9.8.z stable 
> releases); the main commitment here is to the 9 part, indicating 
> Infernalis is the 9th major release cycle.
> 
> Onward!
> 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: 198 bytes --]

  reply	other threads:[~2015-05-04 17:18 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 [this message]
     [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                   ` [ceph-users] " Joao Eduardo Luis

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=5547A9EB.4040404@dachary.org \
    --to=loic@dachary.org \
    --cc=ceph-devel@vger.kernel.org \
    --cc=ceph-users@ceph.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 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.