From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Cooper 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 Message-ID: <557808BA.9010406@citrix.com> References: <55759FF802000078000820F3@mail.emea.novell.com> <1433765948.7108.484.camel@citrix.com> <3FDAE9EB-2D4C-41E2-83D9-B8A21609A267@gmail.com> <1433797194.2388.23.camel@citrix.com> <5576D3C2020000780008284A@mail.emea.novell.com> <8E07AF3D-EE33-45FA-942F-F133FB542D3F@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <8E07AF3D-EE33-45FA-942F-F133FB542D3F@gmail.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Lars Kurth , Jan Beulich Cc: Wei Liu , Ian Campbell , Dario Faggioli , Robert VanVossen , "" , Joshua Whitehead List-Id: xen-devel@lists.xenproject.org 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