From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anthony Liguori Subject: Re: Daily Xen Builds Date: Tue, 11 Oct 2005 17:07:37 -0500 Message-ID: <434C37A9.9070605@us.ibm.com> References: <1128978545.12366.15.camel@dbarrera_tp> <434ADB55.8050609@us.ibm.com> <2b6116b30510111342p1359bd40t21f4bfac54c3c33@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <2b6116b30510111342p1359bd40t21f4bfac54c3c33@mail.gmail.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Nicholas Lee Cc: Ian Pratt , David F Barrera , xen-devel , Dan Smith List-Id: xen-devel@lists.xenproject.org Nicholas Lee wrote: >On 10/11/05, Anthony Liguori wrote: > > >>Is it perhaps wise, nearing 3.0, that we adopt a policy of running the >>various test suites on code before it gets pushed to the public tree? >> >> > > Ian's obviously the best person to answer this but I'll give it a go. >Can we expect there to be a some sort of freeze on 3.0 soon? > > We are sort of already in a testing freeze. There's a lot of activity in the tree because some broken things are being reworked. 2.0 => 3.0 was a pretty significant change in many parts of Xen. A lot changes being made now have associated bugzilla reports. This will likely become the more common case as we move forward. >As a user its hard to tell at the moment if new features are still >being developed and added to 3.0 or we are chasing bugs. > > Yeah, there's a lot of churn in the tree. Most of it is chasing bugs. >The idea that a freeze and focus for release is occurring soon, would >make the time I'm spending testing Xen 3.0 on a machine I want to put >into production at some point is worth while. > >I'm working under the assumption that 3.0 has been projected to be >release soon so its on a spiral to being stable. Otherwise, maybe I'll >just go back 2.0 and wait 6 months. > > This is Open Source. Soon is when-it's-ready. 6 months is probably a safe bet. I would hold your breath to see a release in the next 1-2 months though. Regards, Anthony Liguori >-- >Nicholas Lee >http://stateless.geek.nz >gpg 8072 4F86 EDCD 4FC1 18EF 5BDD 07B0 9597 6D58 D70C > > >