All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dario Faggioli <dario.faggioli@citrix.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>,
	Jan Beulich <JBeulich@suse.com>
Subject: Re: (release) versioning
Date: Wed, 6 May 2015 01:15:25 +0200	[thread overview]
Message-ID: <1430867725.5415.91.camel@citrix.com> (raw)
In-Reply-To: <5548F848.2010701@citrix.com>


[-- Attachment #1.1: Type: text/plain, Size: 2368 bytes --]

On Tue, 2015-05-05 at 18:05 +0100, Andrew Cooper wrote:
> On 05/05/15 16:54, Jan Beulich wrote:
> > All,
> >
> > on the hackathon we also discussed possibly changing the versioning
> > of Xen. The main rationale for the proposal is that (just like in many
> > other software projects) version numbers (in particular the major
> > one) currently don't really convey much information. The proposal is
> > to take gcc's new versioning scheme as a basis (i.e. I'm not going to
> > claim that the below is an exact copy of theirs): Major releases
> > always increment the major version number. Minor version 0 is
> > reserved to the development cycle, i.e. the first release in any
> > release series would be 5.1.0. RCs would be expressed through the
> > 3rd digit, i.e. the first RC of the currently being worked on release
> > would be 5.0.1
>
I like this.

>  (there was some debate as to whether, despite
> > being redundant, to attach -rc1 to it to make clear this is not an
> > actual release).
> >
I see the point of making it clear enough that it's an RC, but then I
don't like the redundancy. I.e., seeing something liek 5.0.1-rc1,
5.0.2-rc2, 5.0.3-rc3 would make me wonder what happened to 5.0.2-rc1, to
5.0.3-rc1 and -rc2 etc.

> > 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
> >
It also feels a bit odd here, still if we keep the -rcX, that 5.0.N-rcN
is the release candidate for 5.1.0... Wouldn't one then be the least
surprised by just seeing the -rcN part dropped and 5.0.N be released?

> > This additionally has the benefit that taking only the numeric
> > part of the version string then would sort properly.
> >
> > Any comments or alternative proposals are welcome.
> 
Well, if we decide to keep the -rcX, then the 3rd digit will be:
 - always .0 for actual releases
 - always the same as -rc* for RCs

so it looks to me that we can just kill it and have:

 5.0-unstable
   5.1-rc1
   5.1-rc2
   ...
   5.1-rcN
 5.1
   5.2-rc1
   ...
 5.3

> +1 (relayed from the hackathon)
> 
All the above being said and FWIW, overall, +1 from me too.

Regards,
Dario

[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  reply	other threads:[~2015-05-05 23:15 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 [this message]
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

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=1430867725.5415.91.camel@citrix.com \
    --to=dario.faggioli@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=andrew.cooper3@citrix.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.