xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Dario Faggioli <dario.faggioli@citrix.com>
To: George Dunlap <george.dunlap@citrix.com>,
	Stefano Stabellini <sstabellini@kernel.org>
Cc: Wei Liu <wei.liu2@citrix.com>,
	xen-devel@lists.xenproject.org,
	Tamas K Lengyel <tamas.lengyel@zentific.com>,
	Tim Deegan <tim@xen.org>, Jan Beulich <jbeulich@suse.com>,
	Andrew Cooper <andrew.cooper3@citrix.com>,
	Anthony Perard <anthony.perard@citrix.com>,
	Ian Jackson <ian.jackson@citrix.com>,
	Roger Pau Monne <roger.pau@citrix.com>
Subject: Re: [PATCH RFC] Add SUPPORT.md
Date: Tue, 12 Sep 2017 10:26:10 +0200	[thread overview]
Message-ID: <1505204770.23667.5.camel@citrix.com> (raw)
In-Reply-To: <48e7d2fd-5081-9a0a-d809-b0bed641a409@citrix.com>


[-- Attachment #1.1: Type: text/plain, Size: 1134 bytes --]

On Mon, 2017-09-11 at 15:16 +0100, George Dunlap wrote:
> On 09/07/2017 10:54 PM, Stefano Stabellini wrote:
> > On Thu, 31 Aug 2017, George Dunlap wrote:
> > > 
> > > +### Null Scheduler
> > > +
> > > +    Status: Experimental
> > > +
> > > 
> > Can we say more than Experimental? I think it should be at least
> > Tech
> > Preview.
> 
> I was going to wait for Dario to respond to this (I had just copied
> what
> was already there).  Tech Preview should look like this:
> 
>     Functional completeness: Yes
>     Functional stability: Quirky
>     Interface stability: Provisionally stable
>     Security supported: No
> 
> I think that's probably accurate.  Dario?
> 
Yes, I think 'Tech Preview' is ok.

Next step would be adding it to OSSTest, at which point, we can start
to think about calling it supported.

Dario
-- 
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)

[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

[-- Attachment #2: Type: text/plain, Size: 127 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

  parent reply	other threads:[~2017-09-12  8:26 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-31 10:27 [PATCH RFC] Add SUPPORT.md George Dunlap
2017-08-31 10:46 ` Paul Durrant
2017-08-31 10:56   ` George Dunlap
2017-08-31 11:03     ` Paul Durrant
2017-08-31 11:05       ` George Dunlap
2017-08-31 11:25 ` Roger Pau Monne
2017-08-31 12:40   ` Jan Beulich
2017-09-07 10:49   ` George Dunlap
2017-09-07 13:57     ` Roger Pau Monné
2017-09-07 14:42       ` George Dunlap
2017-09-07 21:36   ` Stefano Stabellini
2017-09-11 15:54     ` Julien Grall
2017-09-11 16:15       ` George Dunlap
2017-09-11 16:21         ` Julien Grall
2017-08-31 12:46 ` Jan Beulich
2017-09-07 11:31   ` George Dunlap
2017-09-07 11:50     ` Jan Beulich
2017-09-14 17:58       ` Konrad Rzeszutek Wilk
2017-09-07 21:38   ` Stefano Stabellini
2017-09-01 15:00 ` [PATCH RFC] Add SUPPORT.md\ Wei Liu
2017-09-07 13:52   ` George Dunlap
2017-09-07 14:56     ` Wei Liu
2017-09-11 14:22       ` George Dunlap
2017-09-07 21:54 ` [PATCH RFC] Add SUPPORT.md Stefano Stabellini
2017-09-08  9:38   ` Roger Pau Monné
2017-09-08 19:37     ` Stefano Stabellini
2017-09-11 14:16   ` George Dunlap
2017-09-11 15:02     ` Anthony PERARD
2017-09-11 15:07       ` George Dunlap
2017-09-11 15:21         ` Anthony PERARD
2017-09-11 16:16     ` Julien Grall
2017-09-11 16:28       ` George Dunlap
2017-09-11 20:13     ` Rich Persaud
2017-09-11 20:57       ` Stefano Stabellini
2017-09-12  8:26     ` Dario Faggioli [this message]
2017-09-11 16:00   ` Julien Grall
2017-09-11 16:04     ` George Dunlap
2017-09-11 16:39     ` Stefano Stabellini
2017-09-11 18:03       ` Julien Grall

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=1505204770.23667.5.camel@citrix.com \
    --to=dario.faggioli@citrix.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=anthony.perard@citrix.com \
    --cc=george.dunlap@citrix.com \
    --cc=ian.jackson@citrix.com \
    --cc=jbeulich@suse.com \
    --cc=roger.pau@citrix.com \
    --cc=sstabellini@kernel.org \
    --cc=tamas.lengyel@zentific.com \
    --cc=tim@xen.org \
    --cc=wei.liu2@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).