All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Han, Huaitong" <huaitong.han@intel.com>
To: "wei.liu2@citrix.com" <wei.liu2@citrix.com>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Subject: Re: Xen 4.7 Development Update
Date: Wed, 25 Nov 2015 02:17:49 +0000	[thread overview]
Message-ID: <1448417874.4046.10.camel@intel.com> (raw)
In-Reply-To: <E1Zvp6f-0003BK-H9@ukmail1.uk.xensource.com>

On Mon, 2015-11-09 at 16:15 +0000, Wei Liu wrote:
> = 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: July 1, 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 =

== Hypervisor ==
=== x86 ===
*Memory protection keys for user pages
 -Huaitong Han

I want to see it in 4.7, I have sent the 1st version patchset for
review, and continue working on it.

Thanks
Huaitong

  parent reply	other threads:[~2015-11-25  2:17 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-09 16:15 Xen 4.7 Development Update Wei Liu
2015-11-09 16:49 ` Wei Liu
2015-11-10  1:08 ` Xu, Quan
2015-11-10  4:28 ` Juergen Gross
2015-11-11 14:24 ` Anthony PERARD
2015-11-11 14:36 ` Haozhong Zhang
2015-11-25  2:17 ` Han, Huaitong [this message]
2015-12-01 11:54   ` Lars Kurth
2015-12-01 12:35     ` Wei Liu
2015-12-01 12:42       ` Ian Campbell
2015-12-01 12:46         ` Wei Liu
2015-12-01 13:32     ` Yong Wang
2015-12-01 10:34 Wei Liu
2016-01-04 10:15 Wei Liu
2016-01-05  6:57 ` Chun Yan Liu
2016-01-06 13:52   ` Jan Beulich
2016-01-05 14:15 ` Haozhong Zhang
2016-01-05 14:30 ` Meng Xu
2016-01-05 14:34   ` Wei Liu
2016-01-05 16:03     ` Meng Xu
2016-01-07  5:41 ` Haozhong Zhang
2016-01-07 10:21   ` Andrew Cooper
2016-01-07 11:52     ` Jan Beulich
2016-02-01 10:45 Wei Liu
2016-02-01 12:11 ` Jan Beulich
2016-02-01 12:19   ` Wei Liu
2016-02-02  7:38     ` Shuai Ruan
2016-02-03  8:55 ` Haozhong Zhang
2016-02-03  9:36 ` Han, Huaitong
2016-02-03 12:22 ` Olaf Hering
2016-02-29 11:17 Wei Liu
2016-02-29 11:44 ` Jan Beulich
2016-02-29 11:50   ` Wei Liu
2016-02-29 13:27 ` Meng Xu
2016-03-01 22:01   ` Dario Faggioli
2016-02-29 15:35 ` Konrad Rzeszutek Wilk
2016-03-01 10:44   ` Wei Liu
2016-03-02  1:26 ` Han, Huaitong
2016-03-02  3:13 ` Wu, Feng
2016-03-02  5:31 ` Haozhong Zhang
2016-03-02  7:40 ` Shuai Ruan
2016-03-02 11:38 ` George Dunlap
2016-03-02 13:32   ` Jan Beulich
2016-03-02 14:07     ` Paul Durrant
2016-03-02 14:20       ` Jan Beulich
2016-03-02 14:29         ` Paul Durrant
2016-03-02 14:43     ` George Dunlap
2016-03-02 15:07       ` Wei Liu
2016-03-02 14:40 ` Xu, Quan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1448417874.4046.10.camel@intel.com \
    --to=huaitong.han@intel.com \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xenproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.