All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tim Deegan <tim@xen.org>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: (release) versioning
Date: Thu, 7 May 2015 11:54:24 +0100	[thread overview]
Message-ID: <20150507105424.GC40944@deinos.phlegethon.org> (raw)
In-Reply-To: <554903B90200007800076CFC@mail.emea.novell.com>

Hi,

At 16:54 +0100 on 05 May (1430844841), Jan Beulich wrote:
> So comparing current and new schemes things would go
> 
> 	OLD			NEW
> 	4.6-unstable		5.0-unstable (or 5.0.0)
> 	4.6.0-rc1			5.0.1 (-rc1)
> 	...			...
> 	4.6.0-rcN			5.0.N (-rcN)
> 	4.6.0			5.1.0
> 	4.6.1-rc1			5.1.1 (-rc1)
> 	...			...
> 	4.6.1			5.2.0
> 

I prefer the old scheme to the proposed one.  In particular:
 - it's not at all clear to an outsider that 5.0.x is
   unstable and unsupported.
 - main releases of Xen will always be "x.1.0", which makes them
   look like point releases; all the more so because actual point
   releases will be "x.2.0" &c.

If the problem is that the major version number doesn't mean anything,
then we could just drop it.   E.g. more like:

 	OLD			NEW
 	4.6-unstable		6-unstable
 	4.6.0-rc1		6.0-rc1
 	...			...
 	4.6.0-rcN		6.0-rcN
 	4.6.0			6.0
 	4.6.1-rc1		6.1-rc1
 	...			...
 	4.6.1			6.1
        4.7-unstable		7-unstable

> This additionally has the benefit that taking only the numeric
> part of the version string then would sort properly.

With s/6.0/6.0-release/ then the scheme above sorts OK too.  I don't
see why being able to sort RCs based only on the numbers would be
useful.

Tim.

      parent reply	other threads:[~2015-05-07 10:54 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-05 15:54 (release) versioning Jan Beulich
2015-05-05 17:05 ` Andrew Cooper
2015-05-05 23:15   ` Dario Faggioli
2015-05-06 11:54     ` Jan Beulich
2015-05-06 12:45       ` Dario Faggioli
2015-05-06  7:21 ` Wei Liu
2015-05-06  7:25   ` Jan Beulich
2015-05-06 10:37     ` David Vrabel
2015-05-06 10:52       ` Jan Beulich
2015-05-06 10:57         ` David Vrabel
2015-05-06  9:02 ` Ian Campbell
2015-05-06 10:12   ` Jan Beulich
2015-05-06 10:21     ` Ian Campbell
2015-05-06 14:58 ` Konrad Rzeszutek Wilk
2015-05-06 15:19   ` George Dunlap
2015-05-06 15:01 ` George Dunlap
2015-05-06 15:44   ` Jan Beulich
2015-05-06 15:55     ` Lars Kurth
2015-05-07 10:54 ` Tim Deegan [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=20150507105424.GC40944@deinos.phlegethon.org \
    --to=tim@xen.org \
    --cc=JBeulich@suse.com \
    --cc=xen-devel@lists.xenproject.org \
    /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.