From: Lars Kurth <lars.kurth@citrix.com>
To: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>,
"Julien Grall" <julien.grall@linaro.org>,
"Juergen Gross" <jgross@suse.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: Xen_Project_Release_Features page update?
Date: Mon, 15 Jan 2018 14:46:54 +0000 [thread overview]
Message-ID: <42C25BCA-5D9C-449E-AF1B-6960D5EDF4AC@citrix.com> (raw)
In-Reply-To: <20180112203502.GC2935@mail-itl>
Added Juergen and Ian:
On 12/01/2018, 20:36, "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com> wrote:
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.
Correct.
>>
>> 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?
Not yet. It was predicated on:
a) Creation of an equivalent file based on SUPPORT.MD from different branches
b) A tool to create a webpage
> Is there any human-friendly form of SUPPORT.MD?
Not yet: this was meant to happen shortly after the 4.10 release, but Spectre/Meltdown derailed this
Ian Jackson was going to do the work to pull a script together.
I think he may have started (or at least looked at this)
@Ian, @Juergen: we should track this in the 4.11 Release Task list to make sure it doesn’t get dropped
> 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.
Agreed. Now SUPPORT.MD has been migrated and improved from Xen_Project_Release_Features
> Maybe Xen_Project_Release_Features could be automatically generated from
> SUPPORT.MD? Even subset of informations from SUPPORT.MD would be
> useful...
That was the original plan. In fact – once we have backported SUPPORT.md for several releases –
and have the tools, it should be possible to create a table and/or individual pages presenting the
information.
But, as I said, at the moment this is not as important as Spectre/Meltdown fixes
Regards
Lars
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
prev parent reply other threads:[~2018-01-15 14:47 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
2018-01-15 14:46 ` Lars Kurth [this message]
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=42C25BCA-5D9C-449E-AF1B-6960D5EDF4AC@citrix.com \
--to=lars.kurth@citrix.com \
--cc=jgross@suse.com \
--cc=julien.grall@linaro.org \
--cc=marmarek@invisiblethingslab.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.