WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] Release schedule for Xen 4.1

To: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] Release schedule for Xen 4.1
From: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
Date: Wed, 16 Feb 2011 17:13:34 +0000
Cc: Keir Fraser <keir@xxxxxxx>
Delivery-date: Wed, 16 Feb 2011 09:14:25 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Following discussion, and a bit of slip to allow better contributions
from those who've been away for the Chinese New Year, the plan for 4.1
now looks like this.

We intend to go into code freeze at the end of the week, after which
patches even for bugfixes will be much harder to get into the tree.

We are here:

 |   Feature code freeze
 | 
 |     Bugfixes are allowed provided they are not high-risk.
 | 
 |     No new features will be committed.

This is imminent:

 |   Slushy code freeze
 |   after Friday 18 Feb
 | 
 |     Bugfixes are allowed but only if they either:
 |         - fix an important bug; or
 |         - are very trivial and low-risk.
 | 
 |     All changes to receive a formal ack from a maintainer other than
 |     the committer.
 | 
 |   Hard code freeze
 |   after Friday 25 Feb  
 | 
 |     No further patches other than for release-critical bugs.
 | 
 |     All changes to receive a formal ack from a maintainer other than
 |     the committer.
 | 
 |   Release.
 |   planned Monday 7th March
 | 
 |   In all cases, the plan is subject to modification, and to the making
 |   of freeze exceptions by the maintainers following consultation.

Ian.

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

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-devel] Release schedule for Xen 4.1, Ian Jackson <=