All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: (release) versioning
Date: Wed, 6 May 2015 11:21:11 +0100	[thread overview]
Message-ID: <1430907671.2660.198.camel@citrix.com> (raw)
In-Reply-To: <554A054402000078000770C6@mail.emea.novell.com>

On Wed, 2015-05-06 at 11:12 +0100, Jan Beulich wrote:
> >>> On 06.05.15 at 11:02, <ian.campbell@citrix.com> wrote:
> > Adding a trailing redundant -rc (with or without the N) might help, and
> > omitting the N (e.g. "5.0.1-rc") would reduce the redundancy to near
> > zero.
> 
> Good suggestion.
> 
> > Was 5.0-rcN leading to a 5.0 release considered and ruled out?
> 
> It wasn't mentioned in the discussion I think, but ...
> 
> > I suppose
> > it looses the benefit of the numeric portion sorting properly.
> 
> ... based on this I had rules it out before that (and hence didn't
> even bring it up as a possibility). And using 5.0-rcN to lead to a
> 5.1.0 release would become odd/misleading the latest for
> subsequent stable release RCs.

Right, I had meant 5.0-rc leading to a 5.0(.0) release.

(Anyway I'm ok with "5.0.1-rc", so it doesn't matter)
Ian.

  reply	other threads:[~2015-05-06 10:21 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 [this message]
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

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=1430907671.2660.198.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --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.