From: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
To: Julien Grall <julien.grall@linaro.org>
Cc: Lars Kurth <lars.kurth@citrix.com>,
xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: Xen_Project_Release_Features page update?
Date: Fri, 12 Jan 2018 21:35:02 +0100 [thread overview]
Message-ID: <20180112203502.GC2935@mail-itl> (raw)
In-Reply-To: <821b7ccf-95e0-2583-ecaa-2f1a16b8c16e@linaro.org>
[-- Attachment #1.1: Type: text/plain, Size: 1008 bytes --]
On Fri, Jan 12, 2018 at 06:20:05PM +0000, Julien Grall wrote:
> Hi Lars,
>
> As I understand from Xen 4.10 [1] , we are going to use SUPPORT.MD or the
> list of features existing.
>
> I guess we should retire the features matrix [2]? But this also means that
> we have not anymore an easy way to know until when a release is
> supported/security supported. Do you have any plan for this?
Is there any human-friendly form of SUPPORT.MD?
Xen_Project_Release_Features is really convenient place to check about
support for various features. Especially when trying to answer "what Xen
version I need for feature X", or "is my Xen new enough for X"
questions.
Maybe Xen_Project_Release_Features could be automatically generated from
SUPPORT.MD? Even subset of informations from SUPPORT.MD would be
useful...
--
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 157 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2018-01-12 20:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-12 18:20 Xen_Project_Release_Features page update? Julien Grall
2018-01-12 20:35 ` Marek Marczykowski-Górecki [this message]
2018-01-15 14:46 ` 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=20180112203502.GC2935@mail-itl \
--to=marmarek@invisiblethingslab.com \
--cc=julien.grall@linaro.org \
--cc=lars.kurth@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 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).