Made modifications recommended by Chris. Namely:

o Remove stuff that has been done or is now irrelevant.
o Add a reminder to create Release Notes for Release 1.

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@8710 91177308-0d34-0410-b5e6-96231b3b80d8

diff --git a/docs/ReleaseTasks.html b/docs/ReleaseTasks.html
index b721cdb448ffbc6ddc8482c46da697ac7e573718..d09e90cd223bad347f521b078412104a26024cd9 100644 (file)
--- a/docs/ReleaseTasks.html
+++ b/docs/ReleaseTasks.html
@@ -35,7 +35,8 @@ This document is a list of things to do before the LLVM project is
 publicly released.  It will provide a checklist so that we know
 what has been done and what is left to be done.  It will also keep
 a "wishlist" of desirable features.
-  <p><!-- *********************************************************************** --> </p>
+  <p><!-- *********************************************************************** -->
+  </p>
 </ul>
 <table width="100%" bgcolor="#330077" border="0" cellpadding="4"
  cellspacing="0">
@@ -50,7 +51,8 @@ a "wishlist" of desirable features.
 <ul>
 <!-- *********************************************************************** -->The
 list of things to do...
-  <p><!-- ======================================================================= --> </p>
+  <p><!-- ======================================================================= -->
+  </p>
 </ul>
 <table width="50%" bgcolor="#441188" border="0" cellpadding="4"
  cellspacing="0">
@@ -75,6 +77,8 @@ list of things to do...
     <li>Documentation</li>
     <ul>
       <li>Write documentation on the LLVM tools.</li>
+      <li>Create release notes.<br>
+      </li>
       <li>Expand documentation on creating an LLVM project.</li>
       <li>Create a FAQ for common problems.<br>
       </li>
@@ -105,7 +109,8 @@ branching, labeling revisions, etc).</li>
 and support/tools directory.<br>
     </li>
   </ul>
-  <p><!-- ======================================================================= --> </p>
+  <p><!-- ======================================================================= -->
+  </p>
 </ul>
 <table width="50%" bgcolor="#441188" border="0" cellpadding="4"
  cellspacing="0">
@@ -122,7 +127,6 @@ and support/tools directory.<br>
   <ul>
     <li>Improve documentation on how to create an LLVM project.<br>
     </li>
-    <li>Create an installer for the software.</li>
     <li>Test Suite</li>
     <ul>
       <li>Add Feature and Regression tests to nightly tester.</li>
@@ -131,8 +135,6 @@ and support/tools directory.<br>
     </ul>
     <li>Write regression tests.</li>
     <ul>
-      <li>The gccld segfault from GlobalDCE.cpp.</li>
-      <li>The infinite loop for Tail Recursion.</li>
       <li>The C++ constructor on dlopen() bug on Solaris.</li>
     </ul>
   </ul>
@@ -144,7 +146,8 @@ and support/tools directory.<br>
       <li>Find and implement a bug reporting system (i.e. Bugzilla).</li>
     </ul>
   </ul>
-  <p><!-- ======================================================================= --> </p>
+  <p><!-- ======================================================================= -->
+  </p>
 </ul>
 <table width="50%" bgcolor="#441188" border="0" cellpadding="4"
  cellspacing="0">
@@ -163,11 +166,8 @@ and support/tools directory.<br>
     <ul>
       <li>Place the C front end into the CVS repository.</li>
       <li>Ensure that the C front end compiles and installs nicely.</li>
-      <li>Add C++ support.<br>
-      </li>
     </ul>
-    <li>Make the projects/sample directory an actual example of LLVM
-code.</li>
+    <li>Create an installer for the software.</li>
     <li>Testing</li>
     <ul>
       <li>Create descriptions of what each test is doing (test
@@ -176,12 +176,8 @@ specifications).<br>
       <li>Test LLVM on various Linux distributions.</li>
       <li>Test LLVM on various Solaris versions.</li>
       <li>Test LLVM on Solaris/x86.</li>
-      <li>Cleanup Reoptimizer tests so that they fit into the framework.</li>
     </ul>
-    <li>Licenses</li>
     <ul>
-      <li>Create a license for the UIUC specific LLVM code.</li>
-      <li>Add a license file to the distribution file. </li>
     </ul>
     <li>Documentation</li>
     <ul>