From mboxrd@z Thu Jan  1 00:00:00 1970
From: Nivedita Singhvi <niv@us.ibm.com>
Subject: Re: Daily Xen Builds
Date: Mon, 10 Oct 2005 14:32:55 -0700
Message-ID: <434ADE07.7000902@us.ibm.com>
References: <1128978545.12366.15.camel@dbarrera_tp>
	<434ADB55.8050609@us.ibm.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <434ADB55.8050609@us.ibm.com>
List-Unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>, David F Barrera <dfbp@us.ibm.com>, xen-devel <xen-devel@lists.xensource.com>, Dan Smith <danms@us.ibm.com>
List-Id: xen-devel@lists.xenproject.org

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?  
> This seems like requiring passing on xm-test a sane thing to do for the 
> tools related changes.  Is there anything that needs to be done to the 
> test suites to make this less painful for the committers?
> 
> Just to clarify, I'm suggesting that all changes should be checked 
> (external patches or Cambridge pushes) against the testsuites before 
> committing.  Just seems like it would be a good way to ensure that we 
> avoid regressing as we near 3.0 release.

Yep, agree. That will be an additional incentive to get tests up to
speed asap before continuing further work.

thanks,
Nivedita