From: "Jürgen Groß" <jgross@suse.com>
To: xen-devel@lists.xenproject.org, pdurrant@amazon.com
Cc: andrew.cooper3@citrix.com, roger.pau@citrix.com,
luwei.kang@intel.com, marmarek@invisiblethingslab.com,
dwmw@amazon.com
Subject: Re: [Xen-devel] [ANNOUNCE] Xen 4.14 Development Update
Date: Wed, 29 Jan 2020 13:59:50 +0100 [thread overview]
Message-ID: <cb107859-944e-cdf8-e22f-e10aa2a8b613@suse.com> (raw)
In-Reply-To: <20200129123618.1202-1-pdurrant@amazon.com>
On 29.01.20 13:36, Paul Durrant wrote:
> 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
> - David Woodhouse
>
> * Non-Cooperative Live Migration
> - Paul Durrant
Hypervisor file system (v3)
- Juergen Gross
Juergen
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2020-01-29 13:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-29 12:36 [Xen-devel] [ANNOUNCE] Xen 4.14 Development Update 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ß [this message]
2020-01-29 13:04 ` David Woodhouse
2020-01-29 14:12 ` Tamas K Lengyel
2020-01-29 18:03 ` Andrew Cooper
-- strict thread matches above, loose matches on Subject: below --
2020-02-26 10:03 Paul Durrant
2020-03-25 10:19 paul
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=cb107859-944e-cdf8-e22f-e10aa2a8b613@suse.com \
--to=jgross@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=dwmw@amazon.com \
--cc=luwei.kang@intel.com \
--cc=marmarek@invisiblethingslab.com \
--cc=pdurrant@amazon.com \
--cc=roger.pau@citrix.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.