This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] ANNOUNCE: Xen 3.0.5 rename to 3.1.0

To: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] ANNOUNCE: Xen 3.0.5 rename to 3.1.0
From: "Daniel P. Berrange" <berrange@xxxxxxxxxx>
Date: Wed, 2 May 2007 15:02:32 +0100
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 02 May 2007 07:01:57 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <C25E1423.E41E%Keir.Fraser@xxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <C25E1423.E41E%Keir.Fraser@xxxxxxxxxxxx>
Reply-to: "Daniel P. Berrange" <berrange@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.4.1i
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

|=- 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  -=| 

Xen-devel mailing list