From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Lars Kurth <lars.kurth.xen@gmail.com>, Jan Beulich <jbeulich@suse.com>
Cc: Wei Liu <wei.liu2@citrix.com>,
Ian Campbell <Ian.Campbell@citrix.com>,
Dario Faggioli <dario.faggioli@citrix.com>,
Robert VanVossen <Robert.VanVossen@dornerworks.com>,
"<xen-devel@lists.xen.org>" <xen-devel@lists.xen.org>,
Joshua Whitehead <josh.whitehead@dornerworks.com>
Subject: Re: Clarifying the state of ARINC653 scheduler (and other components) in Xen 4.5 and beyond
Date: Wed, 10 Jun 2015 10:51:54 +0100 [thread overview]
Message-ID: <557808BA.9010406@citrix.com> (raw)
In-Reply-To: <8E07AF3D-EE33-45FA-942F-F133FB542D3F@gmail.com>
On 10/06/15 10:42, Lars Kurth wrote:
> Alright,
> if nobody is willing to come up with a definition of experimental/preview/supported/deprecated, I will based on what I have seen
> Lars
I was planning to start a document to this effect to live in
docs/features/, given the success of the command line document.
My plan was that we would slowly gain a doc per feature giving a brief
overflow, support status, further todo for experimental features, etc
which comes with an audit trail of when it moved between supported states.
Of course, this was going to happen in some copus free time intersecting
with a docs day, which hasn't occurred yet :(
~Andrew
next prev parent reply other threads:[~2015-06-10 9:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-08 10:43 Clarifying the state of ARINC653 scheduler (and other components) in Xen 4.5 and beyond Lars Kurth
2015-06-08 12:00 ` Jan Beulich
2015-06-08 12:19 ` Ian Campbell
2015-06-08 13:01 ` Lars Kurth
2015-06-08 20:59 ` Dario Faggioli
2015-06-09 9:53 ` Jan Beulich
2015-06-10 9:42 ` Lars Kurth
2015-06-10 9:51 ` Jan Beulich
2015-06-10 9:51 ` Andrew Cooper [this message]
2015-06-11 16:14 ` Lars Kurth
2015-06-12 15:24 ` Lars Kurth
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=557808BA.9010406@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=Robert.VanVossen@dornerworks.com \
--cc=dario.faggioli@citrix.com \
--cc=jbeulich@suse.com \
--cc=josh.whitehead@dornerworks.com \
--cc=lars.kurth.xen@gmail.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.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.