Difference between revisions of "Xen Project Hypervisor Roadmap/4.5"

From Xen
(Added links to latest blog posts)
(→‎Roadmap on xen-devel: Added description)
Line 15: Line 15:
 
== Roadmap on xen-devel ==
  
== Roadmap on xen-devel ==
 
As in the past, roadmap discussions will mostly happen on the xen-devel mailing list. The convention is that
  
As in the past, roadmap discussions will mostly happen on the xen-devel mailing list. The convention is that
−
* Our release manager will regularly post an e-mail called '''Xen 4.5 development update''' on the list and that community members respond to it. See
 +
* Our release manager will regularly post an e-mail called '''Xen 4.5 development update''' on the list and that community members respond to it.
  +
  +
See
 
* [http://lists.xenproject.org/archives/html/xen-devel/2014-06/msg02597.html Xen 4.5 Development Update (June)]
  
* [http://lists.xenproject.org/archives/html/xen-devel/2014-06/msg02597.html Xen 4.5 Development Update (June)]
−
*
 
 
* [http://lists.xenproject.org/archives/html/xen-devel/2014-05/msg03247.html Xen 4.5 Development Update (May)]
  
* [http://lists.xenproject.org/archives/html/xen-devel/2014-05/msg03247.html Xen 4.5 Development Update (May)]
 
* [http://xen.markmail.org/search/?q=%22Xen+4.4+development+update%22 historical 4.4 roadmap discussions]
  
* [http://xen.markmail.org/search/?q=%22Xen+4.4+development+update%22 historical 4.4 roadmap discussions]
  +
  +
=== The Process ===
  +
If you are working on an item, please respond to the latest <em>Xen 4.5 Development Update</em> on [http://www.xenproject.org/help/mailing-list.html xen-devel]. Work-items are tracked in the following format
  +
  +
<pre>
  +
* <Short description of work item> (<prognosis>)
  +
<optional: detailed description or comment>
  +
- <Name of developer working on the item>
  +
</pre>
  +
  +
The <em>prognosis</em> is now the likelihood of completion in the 4.5 time frame.
  +
  +
* <em>none</em> - nothing yet
  +
* <em>fair</em> - still working on it, patches are prototypes or RFC
  +
* <em>ok</em> - patches posted, acting on review
  +
* <em>good</em> - some last minute pieces
  +
* <em>done</em> - all done, might have bugs
  +
  +
For example:
  +
<pre>
  +
* VMware backdoor (hypercall) (ok)
  +
Needs to be split up and redone
  +
- Don Slutz
  +
</pre>
   
 
[[Category:Xen]]
  
[[Category:Xen]]

Revision as of 12:10, 20 June 2014

Rather than try to predict precisely what will make it into what release (which was something of a disaster last release), I'm just going to borrow a term from the Agile world and call all uncompleted features the "Backlog". I'll still track who is doing what, and when we get close, what state things seem to be in.

Release Manager

We confirmed Konrad Wilk from Oracle as Release Manager for Xen 4.5 : see this e-mail thread

Information about how we manage releases

Roadmap on xen-devel

As in the past, roadmap discussions will mostly happen on the xen-devel mailing list. The convention is that

  • Our release manager will regularly post an e-mail called Xen 4.5 development update on the list and that community members respond to it.

See

The Process

If you are working on an item, please respond to the latest Xen 4.5 Development Update on xen-devel. Work-items are tracked in the following format 

* <Short description of work item> (<prognosis>)
  <optional: detailed description or comment>
  -  <Name of developer working on the item>

The prognosis is now the likelihood of completion in the 4.5 time frame.

  • none - nothing yet
  • fair - still working on it, patches are prototypes or RFC
  • ok - patches posted, acting on review
  • good - some last minute pieces
  • done - all done, might have bugs

For example: 

* VMware backdoor (hypercall) (ok)
  Needs to be split up and redone
  -  Don Slutz
Retrieved from "https://wiki.xenproject.org/index.php?title=Xen_Project_Hypervisor_Roadmap/4.5&oldid=11964"