From: Keir Fraser <keir.fraser@eu.citrix.com>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [ANNOUNCE] Feature freeze for Xen 3.3.0
Date: Fri, 04 Jul 2008 17:46:05 +0100 [thread overview]
Message-ID: <C494125D.23992%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <20080704161439.GA30428@redhat.com>
On 4/7/08 17:14, "Daniel P. Berrange" <berrange@redhat.com> wrote:
> On Fri, Jul 04, 2008 at 03:59:22PM +0100, Keir Fraser wrote:
>> Folks,
>>
>> It's time to freeze xen-unstable in preparation for the 3.3.0 release in
>> August. Anything apart from bug fixes at this stage are likely to
>> be held pending until after 3.3.0 is released.
>
> Is Ian's updated ioemu / qemu tree going to be released in sync wiht 3.3.0
> or is that still being developed/stabilized for a later release ?
It depends if we can get it integrated into the automated test
infrastructure in time. If it's ready next week, we'll consider it still for
3.3.
-- Keir
next prev parent reply other threads:[~2008-07-04 16:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-04 14:59 [ANNOUNCE] Feature freeze for Xen 3.3.0 Keir Fraser
2008-07-04 16:14 ` Daniel P. Berrange
2008-07-04 16:46 ` Keir Fraser [this message]
2008-07-06 3:48 ` Joshua West
2008-07-06 4:59 ` Ian Pratt
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=C494125D.23992%keir.fraser@eu.citrix.com \
--to=keir.fraser@eu.citrix.com \
--cc=berrange@redhat.com \
--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.