From: "Daniel P. Berrange" <berrange@redhat.com>
To: Ewan Mellor <ewan@xensource.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Keir Fraser <keir@xensource.com>,
John Levon <levon@movementarian.org>
Subject: Re: [ANNOUNCEMENT] Schedule for Xen 3.0.4
Date: Fri, 24 Nov 2006 15:54:56 +0000 [thread overview]
Message-ID: <20061124155456.GB29762@redhat.com> (raw)
In-Reply-To: <20061124105812.GB1545@leeni.uk.xensource.com>
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.
--
|=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=|
|=- Perl modules: http://search.cpan.org/~danberr/ -=|
|=- Projects: http://freshmeat.net/~danielpb/ -=|
|=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=|
next prev parent reply other threads:[~2006-11-24 15:54 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-24 10:28 [ANNOUNCEMENT] Schedule for Xen 3.0.4 Keir Fraser
2006-11-24 10:42 ` John Levon
2006-11-24 10:58 ` Ewan Mellor
2006-11-24 15:54 ` Daniel P. Berrange [this message]
2006-11-24 16:34 ` Ewan Mellor
2006-11-24 18:22 ` Daniel P. Berrange
2006-11-28 14:26 ` Ewan Mellor
2006-11-28 14:37 ` Daniel P. Berrange
2006-11-29 17:12 ` Daniel P. Berrange
2006-11-24 12:44 ` Jan Beulich
2006-11-24 18:26 ` Chuck Short
2006-11-29 15:31 ` Sean Dague
2006-11-29 21:36 ` Ian Pratt
2006-11-30 9:05 ` Keir Fraser
2006-11-30 14:59 ` Pasi Kärkkäinen
2006-11-30 15:02 ` Keir Fraser
2006-11-30 15:08 ` Pasi Kärkkäinen
2006-11-30 16:57 ` Keir Fraser
2006-11-30 17:27 ` Ian Pratt
[not found] <4566D99C.5050009@suse.de>
2006-11-24 14:05 ` Keir Fraser
2006-11-24 14:41 ` Gerd Hoffmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20061124155456.GB29762@redhat.com \
--to=berrange@redhat.com \
--cc=ewan@xensource.com \
--cc=keir@xensource.com \
--cc=levon@movementarian.org \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.