[Xen-devel] [ANNOUNCE] Tree freeze for 3.2.0

To:	xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject:	[Xen-devel] [ANNOUNCE] Tree freeze for 3.2.0
From:	Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date:	Wed, 07 Nov 2007 11:58:32 +0000
Delivery-date:	Wed, 07 Nov 2007 03:59:23 -0800
Envelope-to:	www-data@xxxxxxxxxxxxxxxxxx
List-help:	<mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id:	Xen developer discussion <xen-devel.lists.xensource.com>
List-post:	<mailto:xen-devel@lists.xensource.com>
List-subscribe:	<http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe:	<http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender:	xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index:	AcghNYR/wxrVkI0oEdyy3wAX8io7RQ==
Thread-topic:	[ANNOUNCE] Tree freeze for 3.2.0
User-agent:	Microsoft-Entourage/11.3.6.070618

Folks,

I've now finished committing new features into xen-unstable and the tree is
now frozen until after 3.2.0 is released in the next few weeks. No new
features will be accepted at this time; this also applies to the following
pending patches: MSI support (Intel), machine-check support (AMD), PV
scsifront/scsiback (Fujitsu).

Unsurprisingly given the recent churn rate, the tree isn't in a particularly
stable state right now. I will push the staging tree into the main public
tree later today, to encourage wider testing and fixing. Let's aim for a
strong .0 release!

 -- Keir


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

WARNING - OLD ARCHIVES

xen-devel

[Xen-devel] [ANNOUNCE] Tree freeze for 3.2.0