Re: Xen 4.12 Development Update

[Julien Grall <julien.grall@arm.com>]

Hi Juergen,

On 09/11/2018 10:16, Juergen Gross wrote:
> This email only tracks big items for xen.git tree. Please reply for items you
> would like to see in 4.12 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 about every 8 months.
> The upcoming 4.12 timeline are as followed:
> 
> * Last posting date: December 14th, 2018
>    Last posting date for patches touching ARM code: December 1st, 2018
> * Hard code freeze: January 11th, 2019
>    Hard code freeze for patches touching ARM code: December 21st, 2018
> * RC1: TBD
> * Release: March 7th, 2019
> 
> Note that we don't have freeze exception scheme anymore. All patches
> that wish to go into 4.12 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?

> *  dom0less (boot multiple domains from device tree) (v4)
>    -  Stefano Stabellini

This is Arm and not x86.

Other series for Arm:

Implement Set/Way operations (rfc)
    - Julien Grall

TEE mediator (and OP-TEE) support in XEN (v2)
    - Volodymyr_Babchuk@epam.com

Cheers,

-- 
Julien Grall

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