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: "Daniel P. Berrange" <berrange@xxxxxxxxxx>
Subject: Re: [Xen-devel] ANNOUNCE: Xen 3.0.5 rename to 3.1.0
From: Keir Fraser <keir@xxxxxxxxxxxxx>
Date: Wed, 02 May 2007 15:12:10 +0100
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 02 May 2007 07:10:58 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20070502140232.GF9518@xxxxxxxxxx>
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AceMw9+GHcxMWvi3EduO2AAX8io7RQ==
Thread-topic: [Xen-devel] ANNOUNCE: Xen 3.0.5 rename to 3.1.0
User-agent: Microsoft-Entourage/
On 2/5/07 15:02, "Daniel P. Berrange" <berrange@xxxxxxxxxx> wrote:

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

Yes. In an ideal world we would have used this version-numbering scheme in
the first place and made the capability identifiers xen-3-x86_32p etc. Never

 -- Keir

Xen-devel mailing list