From: Keir Fraser <keir@xensource.com>
To: Gerd Hoffmann <kraxel@suse.de>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [ANNOUNCEMENT] Schedule for Xen 3.0.4
Date: Fri, 24 Nov 2006 14:05:10 +0000 [thread overview]
Message-ID: <C18CAC96.4FC4%keir@xensource.com> (raw)
In-Reply-To: <4566D99C.5050009@suse.de>
On 24/11/06 11:38, "Gerd Hoffmann" <kraxel@suse.de> wrote:
> Hi,
>
>> I propose the following schedule: At the end of November we declare the
>> feature freeze. We'd like to get in some more patchsets before this cutoff
>> -- in particular the kexec/kdump patches and the paravirtual framebuffer
>> support.
>
> kexec/kdump means the host kexec?
Yes.
> What about the new domain builder, domU kexec and 32-on-64?
I don't think domU kexec or 32-on-64 will make it. Maybe some of the domain
builder patches could: Emmanuel's been looking those so perhaps he has an
opinion on it, but really I don't see us taking the wholesale rewrite for
3.0.4. After all, the primary benefit is when it's coupled with the 32-on-64
patches which are very unlikely to be in 3.0.4.
However, the advantage of more regular releases is that 3.0.5 won't actually
be that far out. We hope to release that by early March.
-- Keir
> cheers,
> Gerd
next parent reply other threads:[~2006-11-24 14:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4566D99C.5050009@suse.de>
2006-11-24 14:05 ` Keir Fraser [this message]
2006-11-24 14:41 ` [ANNOUNCEMENT] Schedule for Xen 3.0.4 Gerd Hoffmann
2006-11-24 10:28 Keir Fraser
2006-11-24 10:42 ` John Levon
2006-11-24 10:58 ` Ewan Mellor
2006-11-24 15:54 ` Daniel P. Berrange
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-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
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=C18CAC96.4FC4%keir@xensource.com \
--to=keir@xensource.com \
--cc=kraxel@suse.de \
--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.