From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jeremy Fitzhardinge <jeremy@goop.org>
Subject: Testing the kernels
Date: Wed, 25 Aug 2010 15:07:54 -0700
Message-ID: <4C75943A.2000909@goop.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
List-Unsubscribe: <http://lists.xensource.com/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/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: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: "Xen-devel@lists.xensource.com" <Xen-devel@lists.xensource.com>
List-Id: xen-devel@lists.xenproject.org

 So as we discussed, we should split the testing of the toolstack and
the kernel into separate pieces so that kernel failures don't prevent
the toolstack tree from being updated.

I think you should use "xen/next-2.6.32" as the input to the test
subsystem.  If you have a git tree on xenbits with a, say,
"xen/tested-2.6.32" branch which gets updated when the tests pass, then
I can make that automatically update xen/stable-2.6.32.x for public
consumption.

That way people who need/want bleeding edge changes can use
xen/next-2.6.32, and everyone else gets xen/stable-2.6.32.x by default.

    J