From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matt Ayres Subject: Re: RE: New Release Process Date: Fri, 27 Jan 2006 18:18:13 -0500 Message-ID: <43DAAA35.8070306@tektonic.net> References: <43D918B9.1030603@tektonic.net> <2618c79b6f76d8068b52c983b38ce0a4@cl.cam.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <2618c79b6f76d8068b52c983b38ce0a4@cl.cam.ac.uk> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Keir Fraser Cc: Ian Pratt , xen-devel List-Id: xen-devel@lists.xenproject.org Keir Fraser wrote: > > On 26 Jan 2006, at 18:45, Matt Ayres wrote: > >>> Any reason not to call 3.0.1 now? There are a load of bug fixes and >>> improvements over 3.0.0. >> >> I'd say 3.0.1 is required as -unstable has essentially become >> 3.0-testing over the past few weeks. I'd like to see a tree where >> -unstable is truly unstable and not the most stable. > > Upgrading to 2.6.16-rc will probably make your wish come true. ;-) > Current -unstable will become 3.0.1, correct? I am wondering as the Novell guys' CFQ scheduler is turning out to be very useful and with no troubles so far. It'd be nice to get this included in 3.0.1. Thank you, Matt Ayres