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

Re: [Xen-devel] Release plan for 4.1

To: Keir Fraser <keir@xxxxxxx>
Subject: Re: [Xen-devel] Release plan for 4.1
From: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
Date: Thu, 25 Nov 2010 19:15:54 +0000
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 25 Nov 2010 11:17:25 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <C91183D5.AD9E%keir@xxxxxxx>
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>
Newsgroups: chiark.mail.xen.devel
References: <C91183D5.AD9E%keir@xxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Keir Fraser writes ("[Xen-devel] Release plan for 4.1"):
> It's time to start thinking about the release schedule for Xen 4.1. My
> proposal is to freeze the tree for new features at the start of January, and
> start spinning release candidates asap after that, when we are comfortable
> with the stability of the tree. Release should be around 6 weeks after code
> freeze (i.e., we aim for mid-Feb release, or end of Feb at the latest).
> 
> This isn't set in stone yet of course. Opinions welcome!

Can I suggest we stop accepting "big new features" a bit earlier ?

Also, we should be more careful than we have in the past about
accepting many and big changes into late RCs even if they are
allegedly bugfixes.

So I would say, for example, as a rule not to accept fixes for
non-release-critical bugs after the end of February.

Ian.

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