From: Paul Durrant <pdurrant@amazon.com>
To: <xen-devel@lists.xenproject.org>
Cc: jgross@suse.com, andrew.cooper3@citrix.com, pdurrant@amazon.com,
marmarek@invisiblethingslab.com, hongyxia@amazon.com,
jbeulich@suse.com, tamas.k.lengyel@gmail.com,
roger.pau@citrix.com, dwmw@amazon.com
Subject: [Xen-devel] [ANNOUNCE] Xen 4.14 Development Update
Date: Wed, 26 Feb 2020 10:03:51 +0000 [thread overview]
Message-ID: <20200226100351.219-1-pdurrant@amazon.com> (raw)
This email only tracks big items for xen.git tree. Please reply for items
you would like to see in 4.14 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 critical dates for Xen 4.14 are as follows:
---> We are here
* Last posting date: May 1st, 2020
* Hard code freeze: May 22nd, 2020
* Release: June 26th, 2020
Note that we don't have a freeze exception scheme anymore. All patches
that wish to go into 4.14 must be posted initially no later than the
last posting date and finally no later than the hard code freeze.
All patches posted after that date will be automatically queued into next
release.
RCs will be arranged immediately after freeze.
There is also a jira instance to track all the tasks (not only big)
for the project. See: https://xenproject.atlassian.net/projects/XEN/issues.
Some of the tasks tracked by this e-mail also have a corresponding jira task
referred by XEN-N.
There is a version number for patch series associated to each feature.
Can each owner send an update giving the latest version number if the
series has been re-posted? Also, can the owners of any completed items
please respond so that the item can be moved into the 'Completed' section.
= Projects =
== Hypervisor ==
* Live-Updating Xen (RFC v2)
- David Woodhouse
- The latest code is available at https://xenbits.xen.org/gitweb/?p=people/dwmw2/xen.git;a=shortlog;h=refs/heads/lu-master
- Project wiki page at https://wiki.xenproject.org/wiki/Live-Updating_Xen
* Non-Cooperative Live Migration
- Paul Durrant
* Secret Hiding (v5)
- Hongyan Xia
* Hypervisor file system (v3)
- Juergen Gross
=== x86 ===
* Linux stub domains (v4)
- Marek Marczykowski-Górecki
* Virtualise MSR_ARCH_CAPS for guests
- Andrew Cooper
* AMD hardware mitigations (Rome)
- Andrew Cooper
* Xen ioreq server (v3)
- Roger Pau Monne
* Memory read caching in emulation (v4)
- Jan Beulich
* Instruction emulator improvements
- Jan Beulich
* VM forking (v10)
- Tamas K Lengyel
=== ARM ===
== Completed ==
Paul Durrant
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next reply other threads:[~2020-02-26 10:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-26 10:03 Paul Durrant [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-03-25 10:19 [Xen-devel] [ANNOUNCE] Xen 4.14 Development Update paul
2020-01-29 12:36 Paul Durrant
2020-01-29 12:43 ` Marek Marczykowski-Górecki
2020-01-29 12:57 ` Durrant, Paul
2020-01-29 12:47 ` Jan Beulich
2020-01-29 13:00 ` Durrant, Paul
2020-01-29 12:59 ` Jürgen Groß
2020-01-29 13:04 ` David Woodhouse
2020-01-29 14:12 ` Tamas K Lengyel
2020-01-29 18:03 ` Andrew Cooper
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=20200226100351.219-1-pdurrant@amazon.com \
--to=pdurrant@amazon.com \
--cc=andrew.cooper3@citrix.com \
--cc=dwmw@amazon.com \
--cc=hongyxia@amazon.com \
--cc=jbeulich@suse.com \
--cc=jgross@suse.com \
--cc=marmarek@invisiblethingslab.com \
--cc=roger.pau@citrix.com \
--cc=tamas.k.lengyel@gmail.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).