From mboxrd@z Thu Jan  1 00:00:00 1970
From: Keir Fraser <keir@xensource.com>
Subject: Re: ANNOUNCE: Xen 3.0.5 rename to 3.1.0
Date: Wed, 02 May 2007 15:16:58 +0100
Message-ID: <C25E5BEA.E484%keir@xensource.com>
References: <C25E5ACA.E47E%keir@xensource.com>
Mime-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <C25E5ACA.E47E%keir@xensource.com>
List-Unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: xen-devel <xen-devel@lists.xensource.com>
List-Id: xen-devel@lists.xenproject.org




On 2/5/07 15:12, "Keir Fraser" <keir@xensource.com> wrote:

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

But that reminds me that the caps are generated dynamically from major/minor
inside Xen. Argh! I'd better fix that.

 -- Keir