From: Julien Grall <julien.grall@arm.com>
To: Juergen Gross <jgross@suse.com>, xen-devel@lists.xenproject.org
Cc: Stefano Stabellini <sstabellini@kernel.org>,
Volodymyr Babchuk <volodymyr_babchuk@epam.com>
Subject: Re: Xen 4.12 Development Update
Date: Fri, 9 Nov 2018 14:50:20 +0000 [thread overview]
Message-ID: <a733270e-11d7-a544-23dd-a72e0ce19fe1@arm.com> (raw)
In-Reply-To: <20181109101631.5729-1-jgross@suse.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
next prev parent reply other threads:[~2018-11-09 14:50 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-09 10:16 Xen 4.12 Development Update Juergen Gross
2018-11-09 10:40 ` Wei Liu
2018-11-09 10:53 ` Jan Beulich
2018-11-09 18:02 ` Dario Faggioli
2018-11-09 10:56 ` George Dunlap
2018-11-09 11:07 ` Juergen Gross
2018-11-09 11:32 ` George Dunlap
2018-11-09 11:44 ` Andrew Cooper
2018-11-09 12:05 ` Andrew Cooper
2018-11-09 14:50 ` Julien Grall [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-01-14 10:13 Juergen Gross
2019-01-14 10:52 ` Andrew Cooper
2019-01-14 15:22 ` Lars Kurth
2019-01-14 18:09 ` Stefano Stabellini
2018-12-17 14:14 Juergen Gross
2018-12-17 14:40 ` Razvan Cojocaru
2018-12-17 18:38 ` Tamas K Lengyel
2018-11-28 10:26 Juergen Gross
2018-11-28 10:36 ` Andrew Cooper
2018-11-28 15:30 ` Christopher Clark
2018-11-29 20:16 ` Volodymyr Babchuk
2018-11-30 5:34 ` Juergen Gross
2018-11-28 10:15 Juergen Gross
2018-11-28 10:19 ` Juergen Gross
2018-11-28 10:27 ` Paul Durrant
2018-10-08 8:44 Juergen Gross
2018-11-28 6:23 ` Chao Gao
2018-09-12 6:54 Juergen Gross
2018-09-12 8:20 ` Jan Beulich
2018-09-12 8:22 ` Paul Durrant
2018-10-02 19:06 ` Wei Liu
[not found] ` <5B98CC5E02000078001E7A00@suse.com>
2018-09-12 8:30 ` Juergen Gross
2018-09-12 8:41 ` Jan Beulich
2018-07-27 16:19 Juergen Gross
2018-07-31 18:19 ` Rich Persaud
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=a733270e-11d7-a544-23dd-a72e0ce19fe1@arm.com \
--to=julien.grall@arm.com \
--cc=jgross@suse.com \
--cc=sstabellini@kernel.org \
--cc=volodymyr_babchuk@epam.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).