On 13/10/16 12:28, Andrew Cooper wrote: > On 13/10/16 12:01, Dario Faggioli wrote: >> Hey, >> >> "Just" as per the subject, I wrote feature documents for (almost) all our >> schedulers. No big deal, I'd say, apart from the fact that I'm declaring >> Credit2 **Supperted**, instead of experimental. > > Supperted? That's like supported right? ;p > > > It is fine for you to propose that a feature should be upgraded to > supported, and this is probably the best way to formally do so. > > However, final agreement of a feature becoming supported should include > input from the security team. (At the end of the day, it is us with > extra work if the feature isn't up to scratch.)
Yes, interesting idea. I don't think in our discussions of feature lifecycle maturity we'd talked about that yet. -George _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel
