21 messages in com.xensource.lists.xen-develRe: [Xen-devel] [ANNOUNCEMENT] Schedu...
FromSent OnAttachments
Keir Fraser24 Nov 2006 02:28 
John Levon24 Nov 2006 02:42 
Ewan Mellor24 Nov 2006 02:57 
Jan Beulich24 Nov 2006 04:43 
Keir Fraser24 Nov 2006 06:04 
Gerd Hoffmann24 Nov 2006 06:40 
Daniel P. Berrange24 Nov 2006 07:54 
Ewan Mellor24 Nov 2006 08:34 
Daniel P. Berrange24 Nov 2006 10:22 
Chuck Short24 Nov 2006 10:26 
Ewan Mellor28 Nov 2006 06:26 
Daniel P. Berrange28 Nov 2006 06:37 
Sean Dague29 Nov 2006 07:30 
Daniel P. Berrange29 Nov 2006 09:12 
Ian Pratt29 Nov 2006 13:35 
Keir Fraser30 Nov 2006 01:04 
Pasi Kärkkäinen30 Nov 2006 06:59 
Keir Fraser30 Nov 2006 07:01 
Pasi Kärkkäinen30 Nov 2006 07:08 
Keir Fraser30 Nov 2006 08:57 
Ian Pratt30 Nov 2006 09:26 
Subject:Re: [Xen-devel] [ANNOUNCEMENT] Schedule for Xen 3.0.4
From:Daniel P. Berrange (berr@redhat.com)
Date:11/24/2006 07:54:33 AM
List:com.xensource.lists.xen-devel

On Fri, Nov 24, 2006 at 10:58:12AM +0000, Ewan Mellor wrote:

On Fri, Nov 24, 2006 at 10:42:53AM +0000, John Levon wrote:

On Fri, Nov 24, 2006 at 10:28:43AM +0000, Keir Fraser wrote:

release candidates for 3.0.4 once or twice a week until we have a tree suitable for final release (hopefully by the middle of December). Meanwhile

Does this mean we have less than a month until the Xen API work is frozen, as was previously the plan for 3.0.4? We're still discussing aspects of it and AFAIK there's still a lot of work to do in just finishing defining it, never mind coding it or any "can I actually program against this" stuff.

No (sorry for the confusion). Xen 3.0.4 will contain a "preview" of the Xen-API (i.e. what we've got now) but this will not be the final version of the protocol or data-model, and will not be declared stable or supported. We will ensure that the 3.0.3 protocols are supported in 3.0.4, and will take the time during this freeze to make sure that backwards compatibility to 3.0.3-based clients is all in place.

Xen 3.0.4 _will_ contain a working version of "the lifecycle patches", that is, the xm new, start, shutdown, delete, suspend, and resume functionality.

Before 3.0.4 comes out, there are a couple of fixes we previously discussed on xen-api to ensure the lifecycle patches don't break semantics of the existing SEXPR / XMLRPC APIs.

http://lists.xensource.com/archives/html/xen-api/2006-10/msg00009.html

It has also previously been mentioned that XenSource were planning some work on xenstored to address the terrible performance of its transaction code. It'd be nice to see that in 3.0.4 if its ready ?

Dan.