From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anthony Wright Subject: Re: 3.0.3 freeze Date: Tue, 12 Sep 2006 12:06:58 +0100 Message-ID: <450694D2.9030803@communitymesh.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Ian Pratt Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org 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 > >