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 / 4.0.2 plans

To: Keir Fraser <keir@xxxxxxx>
Subject: Re: [Xen-devel] Release plan for 4.1 / 4.0.2 plans
From: Pasi Kärkkäinen <pasik@xxxxxx>
Date: Tue, 23 Nov 2010 21:01:41 +0200
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 23 Nov 2010 11:03:41 -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>
References: <C91183D5.AD9E%keir@xxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.18 (2008-05-17)
On Tue, Nov 23, 2010 at 02:44:37PM +0000, Keir Fraser wrote:
> Folks,
> 
> 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!
> 

Related question: What's the Xen 4.0.2 schedule? 

-- Pasi


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

<Prev in Thread] Current Thread [Next in Thread>