X-Git-Url: http://wien.tomnetworks.com/gitweb/?a=blobdiff_plain;f=web%2Fmono-hacking-roadmap.html;h=0dc6b9a766b0b859e2af2e2b2e93ccf40fcc4a96;hb=b3e0ed93802b80c7105a7d2eb2e9c6e0d7ea38eb;hp=9c822e915f57d9e1cd5b404160c169b7f0d86d70;hpb=06707a449b65e60c261902ee93a4add0861298fb;p=mono.git

diff --git a/web/mono-hacking-roadmap.html b/web/mono-hacking-roadmap.html
index 9c822e915f5..0dc6b9a766b 100644
--- a/web/mono-hacking-roadmap.html
+++ b/web/mono-hacking-roadmap.html
@@ -152,6 +152,13 @@ vertical-align: top;
 	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>
 
@@ -248,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.