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: libxl API changes for 4.2 (Was: Re: [Xen-devel] [PATCH] libxl: do no

To: Christoph Egger <Christoph.Egger@xxxxxxx>
Subject: Re: libxl API changes for 4.2 (Was: Re: [Xen-devel] [PATCH] libxl: do not expose libxenctrl/libxenstore headers via libxl.h)
From: Ian Campbell <Ian.Campbell@xxxxxxxxxxxxx>
Date: Wed, 13 Apr 2011 12:00:50 +0100
Cc: Jim Fehlig <jfehlig@xxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Stefano Stabellini <Stefano.Stabellini@xxxxxxxxxxxxx>, Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>, Beulich <JBeulich@xxxxxxxxxx>, Jan
Delivery-date: Wed, 13 Apr 2011 04:02:12 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4DA576FF.2090805@xxxxxxx>
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Organization: Citrix Systems, Inc.
References: <3aecf852f357e9217144.1302103165@xxxxxxxxxxxxxxxxxxxxx> <19868.35898.53337.358242@xxxxxxxxxxxxxxxxxxxxxxxx> <4D9D9263020000780003A58E@xxxxxxxxxxxxxxxxxx> <1302166342.27835.22.camel@xxxxxxxxxxxxxxxxxxxxxx> <19869.35524.73748.363114@xxxxxxxxxxxxxxxxxxxxxxxx> <alpine.DEB.2.00.1104071122140.3290@kaball-desktop> <4DA52169.5080502@xxxxxxxxxx> <1302689173.5997.22.camel@xxxxxxxxxxxxxxxxxxxxxx> <4DA576FF.2090805@xxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Wed, 2011-04-13 at 11:12 +0100, Christoph Egger wrote:
> On 04/13/11 12:06, Ian Campbell wrote:
> > On Wed, 2011-04-13 at 05:07 +0100, Jim Fehlig wrote:
> >> Stefano Stabellini wrote:
> >>    Seems best for clients
> >> to target new releases (4.1, 4.2, ...) and expect branch releases
> >> (4.1.1, 4.1.2, ...) to have a stable API?
> >
> > That seems like a reasonable expectation to me.
> Any user of libxl should be able to ask for the API version
> and can have different backends for the different API versions then.

In an ideal world, sure. I don't think we have the manpower, test
throughput, etc to implement this sort of scheme for the changes made
post-4.1. Perhaps once the API stabilizes this will become more


Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>