Again, this came up in the developer meeting. This is my last one for today. 
More next week

= Issue / Observation =
Sometimes it is difficult to find out whether a feature is supported (or in 
experimental or other state)
This has an impact on the security team
It also makes life hard for Xen consumers

= Possible Solution / Improvement =
Currently the following two proposal are under discussion

In-tree feature documentation
* http://lists.xenproject.org/archives/html/xen-devel/2015-08/msg02002.html 
<http://lists.xenproject.org/archives/html/xen-devel/2015-08/msg02002.html>
* http://lists.xenproject.org/archives/html/xen-devel/2015-08/msg01995.html 
<http://lists.xenproject.org/archives/html/xen-devel/2015-08/msg01995.html>
* http://lists.xenproject.org/archives/html/xen-devel/2015-08/msg01994.html 
<http://lists.xenproject.org/archives/html/xen-devel/2015-08/msg01994.html>

Proposal: Feature Maturity Lifecycle
* http://lists.xenproject.org/archives/html/xen-devel/2015-06/msg01992.html 
<http://lists.xenproject.org/archives/html/xen-devel/2015-06/msg01992.html>
(Lars to pick this up when the "In-tree feature documentation" has settled 
slightly more - also find a better place for this doc, in-tree)
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Reply via email to