Updated roadmap page

diff --git a/xen.org/products/xen_roadmap.html b/xen.org/products/xen_roadmap.html
index c08288b2b8dff198b5e7aa2e389377c6fff0767a..253f40cda3d1fb25bf23c8d15ed35ec08f3279c3 100644 (file)
--- a/xen.org/products/xen_roadmap.html
+++ b/xen.org/products/xen_roadmap.html
@@ -47,15 +47,43 @@ if(ns4)_d.write("<scr"+"ipt type=text/javascript src=/globals/mmenuns4.js><\/scr
    
  
 <h1>Xen Hypervisor Roadmap</h1>
-<p>As is the case for Linux, the Xen hypervisor developer community does not maintain a roadmap per se. New features
-   that intend to go into the next release are initially announced and discussed on the
-   <b><a href="mailto:xen-devel@lists.xenserver.com">xen-devel mailing list</a></b>.
-   There is also a monthly invite only call to raise issues and discuss bigger development items.
-   If you are planning to implement a feature it is good practice to follow this convention, as otherwise you
-   are running risk that somebody else is implementing a feature already.</p>
-<p>The community and community manager does maintain a wiki page for <a href="http://wiki.xen.org/wiki/Xen_Roadmap">roadmap requests</a>
-   that is planned to become Xen's official roadmap. The Xen 4.3 planning cycle is about to start, but roadmapping will
-   not start until Xen 4.2 release candidates have started.</p>
+<p>As is the case for Linux, the Xen hypervisor developer community does not maintain a committed roadmap as proprietary
+software vendors do. However, the community strives to accurately track development for new Xen releases, with a predictable
+release cadence for major releases and maintenance releases.</p>
+
+<h2>Roadmaps</h2>
+<h3>How contributors operate</h3>
+<p>New features that intend to go into the next release are initially announced and discussed on the
+<b><a href="mailto:xen-devel@lists.xenserver.com">xen-devel mailing list</a></b>.
+There is also a monthly <a href="http://wiki.xen.org/wiki/Xen_Maintainer,_Committer_and_Developer_Meeting">community call</a>
+to raise issues and discuss bigger development items. Invitation to teh call has to be earned. If you are planning to implement
+a feature it is good practice to follow this convention, as otherwise you are running risk that somebody else could have started
+implementing a feature, when you decide to do so.</p>
+
+<h3>How we create a roadmap</h3>
+<p>The community nominates a release manager for each release. During planning and development of a release, the release manager
+sends out regular requests to the xen developer list and asks developers whether they have items to be tracked on the roadmap,
+asks for status updates, etc. The release manager, will however never add a work-item to the <i>roadmap</i> without a developers
+consent. Besiders sending regular updates to the list, we mirror the information posted on the list in a subpage of 
+<a href="http://wiki.xen.org/wiki/Xen_Roadmap">Xen Roadmap</a>.
+
+<h3>Xen 4.3</h3>
+The current list for Xen 4.3 features is published at <a href="http://wiki.xen.org/wiki/Xen_Roadmap/4.3">wiki.xen.org/wiki/Xen_Roadmap/4.3</a>
+or posted on the mailing list under the heading <i>Xen 4.3 development update</i> or <i>Xen 4.3 roadmap</i>.</p>
+
+<h3>Requesting Features</h3>
+<p>Users can request and vote for feature via Xen on Uservoice. For more information, see
+<a href="http://blog.xen.org/index.php/2012/10/15/xen-org-on-uservoice-com/">Xen.org on Uservoice.com</a>.
+Although there is no guarantee that an individual or vendor will step up and implement a feature request,
+a feature that is frequentlu requested is more likely to find an owner who is willing to implement it.</p>
+
+<h2>Release Cadence</h2>
+<p>The Xen developer communtiy aims to release Xen releases at approximately 9 months release cadence.</p>
+
+<h2>Maintenance Releases</h2>
+<p>You can find more information on how the Xen community manages maintenance releases on the
+<a href="http://wiki.xen.org/wiki/Xen_Maintenance_Releases">following wiki page</a>.</p
+
 </table>
 
     <td>&nbsp;</td>