* BinaryFormatter.cs: Added missing methods.

[mono.git] / doc / mono-hacking-roadmap.html

diff --git a/doc/mono-hacking-roadmap.html b/doc/mono-hacking-roadmap.html
index 30e7645e758558a1c5e71739bc38661ea5bed912..0dc6b9a766b0b859e2af2e2b2e93ccf40fcc4a96 100644 (file)
--- a/doc/mono-hacking-roadmap.html
+++ b/doc/mono-hacking-roadmap.html
@@ -148,9 +148,17 @@ vertical-align: top;
                areas missing.
        </ul>
 
-       <p>The team at Novell can probably take care of most of these
-       things (help is always welcomed, of course), letting folks in
-       the open source world working on the more fun components. 
+       <p>The team at Novell will focus on these areas.  We of course
+       welcomes the contribution of the rest of the Mono team and
+       encourage the developers to focus on 1.0, to have a solid
+       release, and a solid foundation that can lead to 1.2
+
+       <p>We will use Bugzilla milestones to track these issues. 
+
+<h3>Synchronized releases</h3>
+
+       <p>It would be great if we can ship Mono 1.0 with Gtk# 1.0 and
+       a preview of Monodoc with the early documentation.  
        
 <h3>Alpha components.</h3>
 
@@ -247,7 +255,7 @@ vertical-align: top;
 <h3>Indigo Plans</h3>
 
        <p>Indigo is still an early product (<a
-       href="http://msdn.microsoft.com/Longhorn/understanding/pillars/Indigo/default.aspx?pull=/library/en-us/dnlong/html/indigofaq1.asp">FAQ</a>,
+       href="http://msdn.microsoft.com/Longhorn/understanding/pillars/Indigo/default.aspx?pull=/library/en-us/dnlong/html/indigofaq1.asp">FAQ</a>),
        but it could benefit from continued development of our WSE1
        and WSE2 components, later to bring some of the code to it.