diff --git a/sfsite/release2_0.html b/sfsite/release2_0.html
index 8f05428ff..268fe7d6d 100644
--- a/sfsite/release2_0.html
+++ b/sfsite/release2_0.html
@@ -55,10 +55,24 @@ goal".  Using the bug database helps to ensure that nothing important gets
 forgotten.  When you're looking at the Source Forge database, you can click on
 the Group box and select just the items that are selected for v2.0.  <p>
 
+
+As the release approaches, we make some pre-release versions with binaries so
+that it's easy for people to try out the new features and check if we've broken
+anything.  These will be called 2.0.pre1, 2.0.pre2, etc.  Meanwhile, we
+continue fixing things, cleaning  up, and trying very hard not to add more bugs
+in the process.  Eventually the developers will agree that we've done enough
+testing and we should go ahead and call it 2.0.
+
 Click to see <a href="http://bochs.sourceforge.net/cgi-bin/topper.pl?name=Report+a+Bug&url=http://sourceforge.net/tracker/qmrkgroup_ideq12580ampatideq112580">Bug Reports</a>.  <br>
 Click to see <a href="http://bochs.sourceforge.net/cgi-bin/topper.pl?name=Request+a+Feature&url=http://sourceforge.net/tracker/qmrkatideq362580ampgroup_ideq12580ampfunceqbrowse">Feature Requests</a>.  <br>
 Click to see <a href="http://bochs.sourceforge.net/cgi-bin/topper.pl?name=Patches&url=http://sourceforge.net/tracker/qmrkatideq312580ampgroup_ideq12580ampfunceqbrowse">Patches</a>.  <br>
 
+
+<BR><font face="arial, helvetica" color="#1e029a" size="4"><b>Try out a 
+Pre-Release </b></font><BR>
+
+
+
  <!--#include virtual="includes/footer.txt" -->