Diff of /releasechecklist [a67a6b] .. [11f472] Maximize Restore

  Switch to side-by-side view

--- a/releasechecklist
+++ b/releasechecklist
@@ -60,21 +60,19 @@
   <ol>
     <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 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. 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.
+your admin user ID.&nbsp; Click on "Files" tab and then click the "Add Folder"
+button.  Name the folder "oprofile-&lt;release&gt;".
+Start with uploading the Release Notes file you created in step 1, but
+first, make a copy of it and rename it to oprofile-&lt;release&gt;_readme.
+Now go into the folder you just created, click the "Add File" button to upload
+the release notes "readme" file. Now click "Add File" and upload
+the new oprofile-&lt;release&gt;.tar.gz file.
    </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
-your release tar ball into that folder.  After creating the next release candidate
-(or GA), cut the tar ball from the previous release candidate folder and paste it
-into oldfiles; then delete the folder it was in.
+    <li>For each successive release candidate (and, eventually, for the GA), upload
+your release tar ball the into the "oprofile-&lt;release&gt;" folder you created above.
+Put a copy of the tar ball from the previous release candidate into the "oldfiles" folder;
+then delete it from the folder it was in.  If the Release Notes file has changed,
+delete the old one and upload the new one.
   </li>
   <li>Go to project download page on SourceForge and verify that
 the new release tar ball is listed there.  It will take some time for
@@ -146,8 +144,9 @@
 	the actual generation of event doc.  Add new .php files in the docs directory for any
 	new processor type that was added since last regeneration.  Also, add a new
 	'do_events ...' line in the all-events-doc.sh file for each new processor type.
-	Now run 'sh all-events-doc.sh' and do a 'git diff'
-	to verify the updates to the docs dir.</li>
+	Now run 'sh all-events-doc.sh'.
+	Finally, edit the doc/index.php file and add a link to each new events PHP file generated.
+	Do a 'git diff' to verify the updates to the docs dir.</li>
 	<li>Verify correctness/completeness
 	of the new release-notes.  Any meaningful change seen when diffing docs/ subdir
 	should be reported in the release-notes file.</li>
@@ -166,12 +165,13 @@
 Shell services (https://sourceforge.net/apps/trac/sourceforge/wiki/Shell%20service).
 See instructions there on how to do ssh and scp.  Then ssh into SF with your admin ID
 and cd to oprofile's www directory
-(/home/project-web/oprofile/htdocs/). There's a git dir there; do a 'git
+(/home/project-web/oprofile/htdocs/). There's a git dir there; CD into that directory and do a 'git
 pull' to update that directory with current data from the shared repo.</li>
     <li>scp the new doc and srcdoc tar balls created in the previous
 step over to SF and untar them into the git dir.</li>
     <li>Ensure that any new files you create have write access for the
-'oprofile' group (do 'chmod g+w' if necessary).</li>
+group (do 'chmod g+w' if necessary).</li>
+    <li>CD into the srcdoc/html directory and copy all files to the parent directory (i.e., "srcdoc").</li>
     <li>Point your browser at http://oprofile.sourceforge.net/git/ and
 verify the website, documentation, etc. looks OK.</li>
     <li>Make a backup of the parent (htdocs) directory; then copy all