On Tue, May 2, 2023 at 12:19 PM Jan Beulich wrote:
> On 28.04.2023 10:12, George Dunlap wrote:
> > --- a/SUPPORT.md
> > +++ b/SUPPORT.md
> > @@ -17,6 +17,36 @@ for the definitions of the support status levels etc.
> > Release Notes
> > : https://wiki.xenproject.org/wiki/Xen_Project_X.YY_Release
On 28.04.2023 10:14, George Dunlap wrote:
> On Fri, Apr 28, 2023 at 9:12 AM George Dunlap wrote:
> It occurred to me that in many (most? all?) cases it would be more
> effective to define the security support parameters in the
> documentation itself.
I think I agree; the alternative of needing to
On 28.04.2023 10:12, George Dunlap wrote:
> --- a/SUPPORT.md
> +++ b/SUPPORT.md
> @@ -17,6 +17,36 @@ for the definitions of the support status levels etc.
> Release Notes
> : href="https://wiki.xenproject.org/wiki/Xen_Project_X.YY_Release_Notes";>RN
>
> +# General security support
> +
> +An XS
On Fri, Apr 28, 2023 at 9:12 AM George Dunlap
wrote:
> The initial goal of SUPPORT.md was to help both users, and the Xen
> Project Security Team, determine what functionality was security
> supported; i.e., what kinds of security bugs would trigger an XSA.
>
> Our proposal is that as of 4.18, al
The initial goal of SUPPORT.md was to help both users, and the Xen
Project Security Team, determine what functionality was security
supported; i.e., what kinds of security bugs would trigger an XSA.
Our proposal is that as of 4.18, all functionality not explicitly
listed as security supported will
