All of lore.kernel.org
 help / color / mirror / Atom feed
From: Loic Dachary <loic@dachary.org>
To: Alex Elsayed <eternaleye@gmail.com>, ceph-devel@vger.kernel.org
Subject: Re: ceph versions
Date: Sat, 28 Feb 2015 00:50:45 +0100	[thread overview]
Message-ID: <54F102D5.5060604@dachary.org> (raw)
In-Reply-To: <mcqs5s$6sr$1@ger.gmane.org>

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



On 27/02/2015 23:47, Alex Elsayed wrote:
> Loic Dachary wrote:
> 
>>
>>
>> On 27/02/2015 13:59, Ilya Dryomov wrote:
>>> On Fri, Feb 27, 2015 at 3:58 AM, Loic Dachary <loic@dachary.org> wrote:
>>>>
>>>>
>>>> On 27/02/2015 00:59, Yehuda Sadeh-Weinraub wrote:
>>>>>
>>>>>
>>>>> ----- Original Message -----
>>>>>> From: "Loic Dachary" <loic@dachary.org>
>>>>>> To: "Sage Weil" <sweil@redhat.com>, ceph-devel@vger.kernel.org
>>>>>> Sent: Thursday, February 26, 2015 3:38:31 PM
>>>>>> Subject: Re: ceph versions
>>>>>>
>>>>>> Hi Sage,
>>>>>>
>>>>>> I prefer Option D because it's self explanatory. We could also drop
>>>>>> the names. I became attached to them but they are confusing to the new
>>>>>> users who is required to remember that firefly is 0.80, giant is 0.87
>>>>>> etc.
>>>>>>
>>>>>> Cheers
>>>>>>
>>>>>> On 27/02/2015 00:12, Sage Weil wrote:
>>>>>>> -- Option D -- "labeled"
>>>>>>>
>>>>>>> X.Y-{dev,rc,release}Z
>>>>>>>
>>>>>>>  - Increment Y on each major named release
>>>>>>>  - Increment X if it's a major major named release (bigger change
>>>>>>> than usual)
>>>>>>>  - Use dev, rc, or release prefix to clearly label what type of
>>>>>>>  release
>>>>>>> this is
>>>>>>>  - Increment Z for stable updates
>>>>>>>
>>>>>>>  1.0-dev1 first infernalis dev release
>>>>>>>  1.0-dev2 another dev release
>>>>>>>  ...
>>>>>>>  1.0-rc1 first rc
>>>>>>>  1.0-rc2 next rc
>>>>>>>  1.0-release1 final release
>>>>>>>  1.0-release2 stable update
>>>>>>>  1.0-release3 stable update
>>>>>>>  1.1-dev1 first cut for j-release
>>>>>>>  1.1-dev2 ...
>>>>>>>  ...
>>>>>>>  1.1-rc1
>>>>>>>  1.1-release1 stable
>>>>>>>  1.1-release2 stable
>>>>>>>  1.1-release3 stable
>>>>>>>
>>>>>>> Q: How do I tell what kind of release this is?
>>>>>>> A: Look at the string embedded in the version
>>>>>>>
>>>>>>> Q: Will these funny strings confuse things that sort by version?
>>>>>>> A: I don't think so.
>>>>>>
>>>>>> dev < rc < release : good pick ;-)
>>>>>>
>>>>>
>>>>> This is the one I lean towards, with one slight variation. I'd drop the
>>>>> 'release' tag and have X.Y[.Z] format for the formal releases, e.g.,
>>>>> 2.0-dev1 first infernalis dev release 2.0-dev2
>>>>> ..
>>>>> 2.0-rc1
>>>>> 2.0-rc2
>>>>> ...
>>>>> 2.0 # infarnalis
>>>>> 2.0.1 # first dot release
>>>>> ...
>>>>> 2.1-dev1 # first j dev release
>>>>> ...
>>>>> 2.1 # j release
>>>>>
>>>>> Then after a few release move to 3.0 to avoid the dreadful big numbers.
>>>>>
>>>>> Sage did mention that this might have some issues in certain
>>>>> environments to sort correctly. Possibly replacing the dash with a
>>>>> tilde solves this?
>>>>>
>>>>
>>>> The lexicographic order of ~ is modified in debian and that may create
>>>> confusion:
>>>>
>>>> http://man.he.net/man5/deb-version
>>>>
>>>>        lexical comparison is a comparison of ASCII values modified so
>>>>        that all
>>>>        the letters sort earlier than all the non-letters and so that  a 
>>>>        tilde
>>>>        sorts  before  anything, even the end of a part.  For example,
>>>>        the fol-
>>>>        lowing parts are in sorted order: '~~', '~~a',  '~',  the  empty 
>>>>        part, 'a'.
>>>>
>>>> The - is lower than the . so it should be good provided the major
>>>> releases are X.Y.0 instead of X.Y, i.e.:
>>>>
>>>> 2.0-rc3
>>>> 2.0.0 # infarnalis
>>>> 2.0.1 # first dot release
>>>>
>>>> etc.
>>>>
>>>> Dropping the "release" word for stable releases is a good idea.
>>>
>>> FWIW I'd lean towards "labeled" scheme without the "release" label as
>>> well.  I don't have a strong opinion on X.Y vs X.Y.0 for formal
>>> releases, but I would have probably gone with X.Y - just my 2c.
>>
>> The problem with X.Y is that it sorts before X.Y-rc3 instead of after.
> 
> Stringwise, yes - though in Exherbo and Gentoo, X.Y-rc3 sorts before X.Y 
> because not all distros treat versions as strings.

Interesting :-) Using X.Y.0 for the first stable release sorts the same, numerically or lexicographically, right ?
> 
> 
> --
> 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-02-27 23:50 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-26 23:12 ceph versions Sage Weil
2015-02-26 23:38 ` Loic Dachary
2015-02-26 23:59   ` Yehuda Sadeh-Weinraub
2015-02-27  0:54     ` Alex Elsayed
2015-02-27  0:58     ` Loic Dachary
2015-02-27 12:59       ` Ilya Dryomov
2015-02-27 13:28         ` Loic Dachary
2015-02-27 13:49           ` Ilya Dryomov
2015-02-27 13:55             ` Loic Dachary
2015-02-27 16:29               ` Yehuda Sadeh-Weinraub
2015-02-27 17:18                 ` Loic Dachary
2015-02-27 22:47           ` Alex Elsayed
2015-02-27 23:50             ` Loic Dachary [this message]
2015-02-28  1:35               ` Alex Elsayed
2015-02-27  0:32 ` Alex Elsayed
2015-02-27  3:52 ` David Moreau Simard
2015-03-02 17:43 ` John Spray
2015-03-30 20:01 ` Sage Weil
2015-03-30 20:09   ` Gregory Farnum

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=54F102D5.5060604@dachary.org \
    --to=loic@dachary.org \
    --cc=ceph-devel@vger.kernel.org \
    --cc=eternaleye@gmail.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.