xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Paul Durrant <Paul.Durrant@citrix.com>
To: 'Julien Grall' <julien.grall@arm.com>,
	"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Subject: Re: Xen 4.10 Development Update
Date: Mon, 21 Aug 2017 10:11:15 +0000	[thread overview]
Message-ID: <2e59656a426f4d1898f6c3369935b948@AMSPEX02CL03.citrite.net> (raw)
In-Reply-To: <E1djjcb-0003ZW-O0@lists.xenproject.org>

> -----Original Message-----
> From: Xen-devel [mailto:xen-devel-bounces@lists.xen.org] On Behalf Of
> Julien Grall
> Sent: 21 August 2017 11:08
> To: xen-devel@lists.xenproject.org
> Cc: julien.grall@arm.com
> Subject: [Xen-devel] Xen 4.10 Development Update
> 
> This email only tracks big items for xen.git tree. Please reply for items you
> woulk like to see in 4.10 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.10 timeline are as followed:
> 
> * Last posting date: September 15th, 2017
> * Hard code freeze: September 29th, 2017
> * RC1: TBD
> * Release: December 2, 2017
> 
> Note that we don't have freeze exception scheme anymore. All patches
> that wish to go into 4.10 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.
> 
> We recently introduced a jira instance to track all the tasks (not only big)
> for the project. See: https://xenproject.atlassian.net/projects/XEN/issues.
> 
> Most of the tasks tracked by this e-mail also have a corresponding jira task
> referred by XEN-N.
> 
> I have started to include the version number of series associated to each
> feature. Can each owner send an update on the version number if the series
> was posted upstream?
> 
> = Projects =
> 
> == Hypervisor ==
> 
> *  Per-cpu tasklet
>   -  XEN-28
>   -  Konrad Rzeszutek Wilk
> 
> *  Add support of rcu_idle_{enter,exit}
>   -  XEN-27
>   -  Dario Faggioli
> 
> === x86 ===
> 
> *  Allow ioreq server interface to support XenGT (v7)
>   -  XEN-43
>   -  Yu Zhang
>   -  Paul Durrant

I think this is either done or obsolete now. Not sure which.

  Paul

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

       reply	other threads:[~2017-08-21 10:11 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1djjcb-0003ZW-O0@lists.xenproject.org>
2017-08-21 10:11 ` Paul Durrant [this message]
2017-08-21 10:15   ` Xen 4.10 Development Update Julien Grall
2017-08-22 10:22     ` Yu Zhang
2017-08-22 12:44       ` Julien Grall
2017-08-23  2:29         ` Yu Zhang
2017-08-21 17:32 ` Konrad Rzeszutek Wilk
     [not found] <E1djjcb-0003ZW-Ic@lists.xenproject.org>
2017-08-22 13:56 ` Meng Xu
     [not found] <E1djjcb-0003ZW-LY@lists.xenproject.org>
2017-08-22  5:59 ` Oleksandr Andrushchenko
2017-08-22 12:34   ` Julien Grall
     [not found] <59c5a995.016@prv1-mh.provo.novell.com>
2017-08-21 12:34 ` Jan Beulich
2017-08-21 10:07 Julien Grall
2017-08-21 10:26 ` Juergen Gross
     [not found] <E1dX62i-0000PQ-5X@lists.xenproject.org>
2017-07-20  9:14 ` Yi Sun
     [not found] <E1dX62i-0000PQ-8Y@lists.xenproject.org>
2017-07-19 15:32 ` Daniel Kiper
2017-07-20 16:57   ` Manish Jaggi
2017-07-20 17:27     ` Julien Grall
2017-07-26 15:12       ` Oleksandr Tyshchenko
  -- strict thread matches above, loose matches on Subject: below --
2017-07-17 13:26 Julien Grall

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=2e59656a426f4d1898f6c3369935b948@AMSPEX02CL03.citrite.net \
    --to=paul.durrant@citrix.com \
    --cc=julien.grall@arm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).