All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Wright <anthony@communitymesh.com>
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com
Subject: Re: 3.0.3 freeze
Date: Tue, 12 Sep 2006 12:06:58 +0100	[thread overview]
Message-ID: <450694D2.9030803@communitymesh.com> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D5724D7@liverpoolst.ad.cl.cam.ac.uk>

Hi Ian,

It's three weeks since you posted this message. I wondered if you could 
post an update?

Thanks,
Tony Wright.

Ian Pratt wrote:
> Folks,
>
> I think its time to declare a 3.0.3 feature freeze. We've got all the
> 'must have' feature patches in -unstable and many of the 'would be nice'
> variety too.
>
> Just to summarize, we have: the new scheduler, blktap with file-based VM
> storage, upgraded device emulation, new shadow pagetable code, PV
> drivers for HVM guests, networking support for segmentation offload,
> support for the Power architecture, misc performance optimizations and
> bug fixes.
>
> There were a number of patches that haven't quite made the cut off due
> to various outstanding issues or lack of review time: The NUMA allocator
> patch has been observed to cause problems on at least one system. The PV
> framebuffer could do with a few interface tweaks and a code cleanup. The
> kexec/kdump patch just needs more testing [I feel bad about this one --
> maybe we can retrofit it]. The xend lifecycle management patches will be
> held-over to the next release so it can become part of a larger set of
> control tool changes.
>
> Now the tree is in 'freeze' state, please can everyone get ready to do
> some serious testing. We're still working on a handful of known issues
> we can reproduce, so this message isn't quite a full call to arms for
> testing from the user community yet, but it would be great if developers
> could start giving it a workout.  
>
> Thanks,
> Ian
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
>   

  parent reply	other threads:[~2006-09-12 11:06 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-22 16:03 3.0.3 freeze Ian Pratt
2006-08-22 16:34 ` Sean Dague
2006-08-22 21:00 ` Ryan Harper
2006-08-22 21:12   ` Subrahmanian, Raj
2006-08-25  0:53 ` Tuan Van
2006-08-28 14:58 ` Daniel P. Berrange
2006-08-28 15:08   ` Keir Fraser
2006-08-28 15:21     ` Daniel P. Berrange
2006-08-28 15:49     ` Daniel Veillard
2006-08-28 16:32       ` Keir Fraser
2006-08-28 16:47         ` Rik van Riel
2006-08-28 16:48           ` Keir Fraser
2006-08-28 17:12             ` Rik van Riel
2006-08-28 17:19               ` Keir Fraser
2006-08-28 17:56         ` Daniel Veillard
2006-09-12 11:06 ` Anthony Wright [this message]
2006-09-12 11:40   ` Ian Pratt
2006-09-12 12:55     ` Anthony Wright
2006-09-12 13:45       ` Matt Ayres
2006-09-12 22:00         ` John Lenz
2006-09-13  9:33           ` Nicholas Lee
2006-09-19 11:21     ` Anthony Wright
2006-09-19 12:56       ` Keir Fraser
  -- strict thread matches above, loose matches on Subject: below --
2006-08-28 15:22 Ian Pratt
2006-08-28 16:48 Ian Pratt
2006-08-28 17:03 ` Daniel P. Berrange
2006-08-28 20:16 ` Daniel Veillard

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=450694D2.9030803@communitymesh.com \
    --to=anthony@communitymesh.com \
    --cc=m+Ian.Pratt@cl.cam.ac.uk \
    --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.