2004-02-07 Miguel de Icaza <miguel@ximian.com>

[mono.git] / web / mono-roadmap.html

diff --git a/web/mono-roadmap.html b/web/mono-roadmap.html
index b5679ea903f9c9f855adbe15e7c4991a5c28f43a..c57b040b05882f22d5d61d2c2c75ca5362c3bf1e 100644 (file)
--- a/web/mono-roadmap.html
+++ b/web/mono-roadmap.html
@@ -73,6 +73,8 @@ vertical-align: top;
   <p>
 </center>
 
+<i>Last update: Jan 18th, 2004</i>
+
 <h3>Introduction</h3>
 
        <p>This document describes the high-level roadmap for <a
@@ -89,7 +91,7 @@ vertical-align: top;
        <p>At the October 2003 PDC conference a number of new
        technologies were announced.  From the Mono release schedule
        perspective, we should think about these technologies from
-       their release time perspective, and the features that must be
+       their release time standpoint, and the features that must be
        supported.
 
        <p>This document outlines the roadmap for the Mono project
@@ -99,11 +101,17 @@ vertical-align: top;
        into the plan if external sources devote enough attention to
        those problems.
 
+       <p>This is the timeline:
+       <p>
+       <center>
+       <img src="roadmap.png">
+       </center>
+       
 <h3>Background</h3>
 
        <p>So far Microsoft has published two versions of the .NET
        Framework: 1.0 and 1.1, the later with incremental updates to
-       the changes in 1.1.
+       the changes in 1.0
 
        <p>The Mono project has been tracking some of the
        improvements available in those two releases, some of the
@@ -131,7 +139,7 @@ vertical-align: top;
        various people.
 
        <p>Some other smaller and less used components do not have yet
-       a Mono equivalent.
+       a Mono equivalent (System.Management, System.Drawing.Design).
 
 <h3>Mono release strategy</h3>
 
@@ -139,7 +147,7 @@ vertical-align: top;
        development effort we have put into it, and the use we have
        given to them.  For example, the virtual machine and the C#
        compiler very mature, while less commonly used functionality
-       like Windows.Forms or VB.NET are still under heavy
+       in Mono like Windows.Forms or VB.NET are still under heavy
        development.
 
        <p>Our strategy is to release the mature components as Mono
@@ -179,6 +187,10 @@ vertical-align: top;
                <li>ECMA profiles: special build options to build
                Mono as an implementation of the various ECMA profiles
                will be available.
+
+               <li>Java integration through IKVM.
+
+               <li>Embedding interface for the runtime.
        </ul>
 
        <p>Packaging:
@@ -196,13 +208,19 @@ vertical-align: top;
                other technologies under development for developer's
                convenience, but will be unsupported at this time.
                These include the Generics edition of the C#
-               compiler. 
+               compiler.
+
+               <li>mono-ecma: A build that only includes the ECMA
+               components.
        </ul>
        
-       <p>Release schedule: Q1/2004 release.
+       <p>Release target: Q2/2004.
 
        <p>Bug fix releases would be done on a monthly basis.
 
+       <p>For a detailed list, see the <a
+       href="mono-1.0.html">mono-1.0 feature list.</a>
+
 <h3>Microsoft's Whidbey</h3>
 
        <p>To understand post 1.0 editions of Mono, it is important to
@@ -257,7 +275,7 @@ vertical-align: top;
        <p>Mostly, Mono 1.2 consists of components that were not
        stable enough for Mono 1.0, but that would be mature at this
        point, plus the incorporation of some new features from
-       Whidbey.  In addition to the Mono 1.9 components, this release
+       Whidbey.  In addition to the Mono 1.0 components, this release
        will add:
 
        <ul>
@@ -268,7 +286,8 @@ vertical-align: top;
 
                <li>Remoting improvements from Whidbey.
 
-               <li>System.XML improvements from Whidbey, most likely missing XQuery.
+               <li>System.XML: simpler improvements from Whidbey,
+               lacking the large additions (XQuery for example).
 
                <li>Console and Serial ports support.
 
@@ -276,7 +295,8 @@ vertical-align: top;
 
                <li>WSE1/WSE2 implementations.
 
-               <li>System.Windows.Forms officially debuts.
+               <li>System.Windows.Forms officially debuts with .NET
+               1.0 API;  1.2 API available as an unstable addition.
        </ul>
 
        <p>This release will by default provide .NET 1.2 APIs, but
@@ -285,14 +305,23 @@ vertical-align: top;
        be distributed on the `mono-unstable' package, the libraries
        in this release will be unsupported. 
 
-       <p>Release schedule: Q3/2004 release.
+       <p>Release target: Q4/2004.
+
+<h3>Mono 1.4</h3>
 
+       <p>A refresh update on the Mono 1.2 release containing the
+       missing components from the previous release and complete any
+       under performing pieces.  Updates to System.Xml, ASP.NET and
+       Windows.Forms to match the .NET 1.2 API.
+
+       <p>Release target: Q2/2005.
+       
 <h3>Peer projects</h3>
 
-       <p>Other projects like the debugger, the documentation browser
-       and Gtk# will remain on their own schedules.   This page will
-       be updated to contain that information when it becomes
-       available.
+       <p>Other projects like the debugger, the documentation
+       browser, Java integration through IKVM and Gtk# will remain on
+       their own schedules.  This page will be updated to contain
+       that information when it becomes available.
 
 <h3>Unscheduled activities</h3>