All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: ANNOUNCE: Xen 3.0.5 rename to 3.1.0
Date: Wed, 2 May 2007 15:02:32 +0100	[thread overview]
Message-ID: <20070502140232.GF9518@redhat.com> (raw)
In-Reply-To: <C25E1423.E41E%Keir.Fraser@cl.cam.ac.uk>

On Wed, May 02, 2007 at 10:10:43AM +0100, Keir Fraser wrote:
> Folks,
> 
> The imminent next Xen release introduces a host of important new features
> including PV 32-on-64, HVM save/restore, and XenAPI 1.0. Now is a good time
> to bump our version number and reclaim the redundant second digit!
> 
> We plan to rename the xen-3.0.5-testing.hg tree to xen-3.1.0-testing later
> today. The release candidate will be renamed to 3.1.0-rc4. The final release
> will be called 3.1.0 (as opposed to 3.0.5-0 in the old numbering scheme).
> Further bug-fix releases in the 3.1 series will be called 3.1.x (as opposed
> to 3.0.5-x in the old numbering scheme).

Sounds like a good plan - makes it simpler to fit it in with RPM version
numbering too.

> This change rationalises and simplifies our version numbering scheme. It
> avoids the need for the fourth digit "-x", and incrementing the second
> rather than third digit makes it clearer that large changes, not just bug
> fixes, are incorporated in our quarterly major releases.

What is the relationship now between the hypervisor kernel capability
version numbers & the software release numbers ? I assume the HV ABI
versions should be considered to be decoupled now & they'll stay on
a value of 3.0 ? 

$ cat /sys/hypervisor/properties/capabilities 
xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p

Regards,
Dan.
-- 
|=- Red Hat, Engineering, Emerging Technologies, Boston.  +1 978 392 2496 -=|
|=-           Perl modules: http://search.cpan.org/~danberr/              -=|
|=-               Projects: http://freshmeat.net/~danielpb/               -=|
|=-  GnuPG: 7D3B9505   F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505  -=| 

  reply	other threads:[~2007-05-02 14:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-02  9:10 ANNOUNCE: Xen 3.0.5 rename to 3.1.0 Keir Fraser
2007-05-02 14:02 ` Daniel P. Berrange [this message]
2007-05-02 14:12   ` Keir Fraser
2007-05-02 14:16     ` Keir Fraser
2007-05-02 21:33       ` Cédric Schieli
2007-05-02 21:38         ` Daniel P. Berrange
2007-05-02 21:43           ` Brendan Cully
2007-05-02 21:53             ` Daniel P. Berrange
2007-05-02 21:58               ` Brendan Cully
2007-05-07  6:14 ` Jun Koi

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=20070502140232.GF9518@redhat.com \
    --to=berrange@redhat.com \
    --cc=Keir.Fraser@cl.cam.ac.uk \
    --cc=xen-devel@lists.xensource.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.