From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Jan Beulich" Subject: Re: Xen 4.4 development update -- RFC for feature freeze timeline Date: Fri, 27 Sep 2013 08:41:12 +0100 Message-ID: <524552B802000078000F7463@nat28.tlf.novell.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VPSfT-0003yd-Fd for xen-devel@lists.xenproject.org; Fri, 27 Sep 2013 07:40:51 +0000 In-Reply-To: Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: George Dunlap Cc: xen-devel List-Id: xen-devel@lists.xenproject.org >>> On 26.09.13 at 18:47, George Dunlap wrote: > Nonetheless, it does seem likely that delaying for a month may allow a > significant number of important features to get in. > > Any thoughts? I'm in favor of pushing back by a month as long as this allows at least a fair share of the listed pending things to go in. An alternative would be a weak feature freeze (no new features except for a well defined set) on the original date, but that would certainly undermine the stabilizing phase to some degree. Jan