Diff of /releasechecklist [22713e] .. [0cae41] Maximize Restore

  Switch to side-by-side view

--- a/releasechecklist
+++ b/releasechecklist
@@ -58,14 +58,17 @@
     Make a release (candidate) publicly available.
  
   <ol>
-    <li>With a browser, go to OProfile website and click on the
+    <li>With a browser, go to the OProfile website and click on the
 "SOURCEFORGE.NET" at the bottom left of the screen.&nbsp; Sign in with
 your admin user ID.&nbsp; Click on "Develop" and then "File Manager" from the
-"Proejct Admin" menu.  Click on the "Help" link and follow the instructions
-to upload the new oprofile-&lt;release&gt;.tar.gz file
-to SourceForge. Upload the release file as well, but rename it to
+"Proejct Admin" menu.  Click on the "Help" link and follow the instructions to
+upload files.  Start by uploading the release file, but rename it to
 oprofile-&lt;release&gt;-rel-notes so that it's obvious to users who
-browse the project files. 
+browse the project files. Click on the release notes file you just uploaded, and then
+check the "Release note" box in "File details" -- and press "Save".  Then upload
+the new oprofile-&lt;release&gt;.tar.gz file and, using the "Release notes for
+this file" drop-down list box, associate this file
+with the release notes file you previously uploaded.
    </li>
     <li>For each successive release candidate (and, eventually, for the GA), create a
 new folder, based on the release name (e.g., oprofile-0.9.5-rc1) and upload
@@ -172,7 +175,7 @@
 'oprofile' group (do 'chmod g+w' if necessary).</li>
     <li>Point your browser at http://oprofile.sourceforge.net/cvs/ and
 verify the website, documentation, etc. looks OK.</li>
-    <li>Make a backup of the parent (htdocs) directory; then move all
+    <li>Make a backup of the parent (htdocs) directory; then copy all
 the stuff from the cvs dir into the parent dir to make it live.&nbsp;
 Now use your browser to verify that the actual OProfile website looks
 OK.<br>