All of lore.kernel.org
 help / color / mirror / Atom feed
From: Meng Xu <xumengpanda@gmail.com>
To: Wei Liu <wei.liu2@citrix.com>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Subject: Re: Xen 4.7 Development Update
Date: Mon, 29 Feb 2016 08:27:57 -0500	[thread overview]
Message-ID: <CAENZ-+ksAoDmV-99ot+OnD+VG0DhktDkCmXhBSy0neQPAqRjCA@mail.gmail.com> (raw)
In-Reply-To: <E1aaLp3-0001zx-6u@zion>

On Mon, Feb 29, 2016 at 6:17 AM, Wei Liu <wei.liu2@citrix.com> wrote:
> NOTE: We are one month away from freeze. Features that wish to be in 4.7 must
> be posted to xen-devel by March 18.
>
> 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 =
>
> == Hypervisor ==
>
> *  Convert RTDS from time to event-driven model
>   -  Meng Xu
>   -  Tianyang Chen

We will try our best to meet this release cycle, although we are not
very sure if we can definitely meet the deadline. The patch is in a
correct direction and is in a good state, though.

Dario, what do you think? If we move faster this week in resolving the
comments, is there any chance that we could potentially finish it?

Thanks,

Meng

-----------
Meng Xu
PhD Student in Computer and Information Science
University of Pennsylvania
http://www.cis.upenn.edu/~mengxu/

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  parent reply	other threads:[~2016-02-29 13:27 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-29 11:17 Xen 4.7 Development Update Wei Liu
2016-02-29 11:44 ` Jan Beulich
2016-02-29 11:50   ` Wei Liu
2016-02-29 13:27 ` Meng Xu [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
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-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
2015-12-01 10:34 Wei Liu
2015-11-09 16:15 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
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

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=CAENZ-+ksAoDmV-99ot+OnD+VG0DhktDkCmXhBSy0neQPAqRjCA@mail.gmail.com \
    --to=xumengpanda@gmail.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.