[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

  • To: "Keir Fraser" <keir@xxxxxxxxxxxxx>
  • From: "Cédric Schieli" <cschieli@xxxxxxxxx>
  • Date: Wed, 2 May 2007 23:33:04 +0200
  • Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Wed, 02 May 2007 14:31:35 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=Nq8x2/86BmH0aGZKmh60VuHYoIT70g3EeBEthqWyYzGNdw0EA3h3OS54Hx9RXXx1LaWaUVoHGSVADvhLyLzRcExEX4IcbQwY27fvD/Pm3YFQeMfbttfhW0D/MgSZzXm43CSIZLzvIj7PQ1lLlyTboC8Ymn56mkFiAopIU7vT6fE=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Shouldn't the various library sonames (libblktap, libxenctrl, libxenguest, libxutil, libxenstore) also be bumped to 3.1 ?


2007/5/2, Keir Fraser < keir@xxxxxxxxxxxxx>:

On 2/5/07 15:12, "Keir Fraser" < keir@xxxxxxxxxxxxx> 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

Xen-devel mailing list

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.