[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: "Daniel P. Berrange" <berrange@xxxxxxxxxx>
  • 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
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AceMw9+GHcxMWvi3EduO2AAX8io7RQ==
  • Thread-topic: [Xen-devel] ANNOUNCE: Xen 3.0.5 rename to 3.1.0

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



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