From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Han, Huaitong" Subject: Re: Xen 4.7 Development Update Date: Wed, 3 Feb 2016 09:36:23 +0000 Message-ID: <1454492193.4350.3.camel@intel.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1aQtrR-0001gz-K6 for xen-devel@lists.xenproject.org; Wed, 03 Feb 2016 09:36:29 +0000 In-Reply-To: Content-Language: en-US Content-ID: <6E595573C7FA1E4B9DD2BB6334A39F75@intel.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: "xen-devel@lists.xenproject.org" , "wei.liu2@citrix.com" List-Id: xen-devel@lists.xenproject.org On Mon, 2016-02-01 at 10:45 +0000, Wei Liu wrote: > This email only tracks big items for xen.git tree. Please reply for > items you > woulk like to see in 4.7 so that people have an idea what is going on > and > prioritise accordingly. > > You're welcome to provide description and use cases of the feature > you're > working on. > > = Timeline = > > We now adopt a fixed cut-off date scheme. We will release twice a > year. The upcoming 4.7 timeline are as followed: > > * Last posting date: March 18, 2016 > * Hard code freeze: April 1, 2016 > * RC1: TBD > * Release: June 3, 2016 > > Note that we don't have freeze exception scheme anymore. All patches > that wish to go into 4.7 must be posted no later than the last > posting > date. All patches posted after that date will be automatically queued > into next release. > > RCs will be arranged immediately after freeze. > > = Projects = > * Memory protection-key support > - Huaitong Han V8 (7 patches) has been sent out, 2 patches have already been merged, 3 of the remaining 5 patches have been Acked/Reviewed by Andrew/Jan.