All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keir Fraser <keir@xensource.com>
To: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: [ANNOUNCEMENT] Schedule for Xen 3.0.4
Date: Fri, 24 Nov 2006 10:28:43 +0000	[thread overview]
Message-ID: <C18C79DB.4F96%keir@xensource.com> (raw)

Folks,

The xen-unstable tree has seen significant progress since 3.0.3 was forked,
particularly in HVM cleanup and bug fixing. SMP and ACPI HVM guests now work
reliably, as does the Windows Vista installer. Many of these improvements
are the result of large patches and interface cleanups that are unsuitable
for backporting to 3.0.3. Since we'd like to make these improvements
available to Xen users as soon as possible, now seems a good time to call a
feature freeze in preparation for 3.0.4.

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. Following this, and depending on good testing results, we tag
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
we focus on any lurking performance and correctness bugs that have been
introduced during the recent spike in check-in activity.

These plans are part of a more general move to more frequent Xen releases.
By shortening the development phase of our release cycle we can keep tighter
tabs on the status of the Xen tree, resulting in better prediction of
release dates and faster release of new features and enhancements to the Xen
user community!

 Cheers,
 Keir (and the Xen team)

             reply	other threads:[~2006-11-24 10:28 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-24 10:28 Keir Fraser [this message]
2006-11-24 10:42 ` [ANNOUNCEMENT] Schedule for Xen 3.0.4 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-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=C18C79DB.4F96%keir@xensource.com \
    --to=keir@xensource.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.