Re: [Xen-devel] Xen 4.10 Development Update

[Yu Zhang <yu.c.zhang@xxxxxxxxxxxxxxx>]

On 8/22/2017 8:44 PM, Julien Grall wrote:
> Hi,
>
> On 22/08/17 11:22, Yu Zhang wrote:
> > On 8/21/2017 6:15 PM, Julien Grall wrote:
> > > Hi Paul,
> > >
> > > On 21/08/17 11:11, Paul Durrant wrote:
> > > > > -----Original Message-----
> > > > > From: Xen-devel [mailto:xen-devel-bounces@xxxxxxxxxxxxx] On Behalf Of
> > > > > Julien Grall
> > > > > Sent: 21 August 2017 11:08
> > > > > To: xen-devel@xxxxxxxxxxxxxxxxxxxx
> > > > > Cc: julien.grall@xxxxxxx
> > > > > 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.
> > > CCed Yu Zhang to tell which one.
> > Thanks, Julien. This is done now. :)
> I may have messed up with the update. Was it upstreamed for Xen 4.9 or 
> Xen 4.10? For the former, I will just totally remove it from the update.
It was merged in Xen 4.9. We can just remove this from the update. :-)

Thanks
Yu

> Cheers,

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