[prev in list] [next in list] [prev in thread] [next in thread] 

List:       oprofile-commits
Subject:    [oprof-cvs] CVS: oprofile-www ChangeLog, 1.107,
From:       "Maynard Johnson" <maynardj () users ! sourceforge ! net>
Date:       2009-11-24 20:53:58
Message-ID: E1ND2Oc-0005dd-3l () sfp-cvsdas-1 ! v30 ! ch3 ! sourceforge ! com
[Download RAW message or body]

Update of /cvsroot/oprofile/oprofile-www
In directory sfp-cvsdas-1.v30.ch3.sourceforge.com:/tmp/cvs-serv21631

Modified Files:
	ChangeLog releasechecklist 
Log Message:
Updated instructions for clarity

Index: ChangeLog
===================================================================
RCS file: /cvsroot/oprofile/oprofile-www/ChangeLog,v
retrieving revision 1.107
retrieving revision 1.108
diff -u -p -d -r1.107 -r1.108
--- ChangeLog	24 Nov 2009 18:39:57 -0000	1.107
+++ ChangeLog	24 Nov 2009 20:53:52 -0000	1.108
@@ -1,5 +1,9 @@
 2009-11-24  Maynard Johnson  <maynardj@us.ibm.com>
 
+	* releasechecklist: Updated instructions for clarity
+
+2009-11-24  Maynard Johnson  <maynardj@us.ibm.com>
+
 	* credits/index.php: Update maintainer information
 
 2009-11-24  Maynard Johnson  <maynardj@us.ibm.com>

Index: releasechecklist
===================================================================
RCS file: /cvsroot/oprofile/oprofile-www/releasechecklist,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -p -d -r1.12 -r1.13
--- releasechecklist	3 Aug 2009 14:47:34 -0000	1.12
+++ releasechecklist	24 Nov 2009 20:53:53 -0000	1.13
@@ -58,14 +58,17 @@ you specified in AM_INIT_AUTOMAKE.<br>
     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 @@ step over to SF and untar them into the 
 '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>


------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Oprofile-commits mailing list
Oprofile-commits@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oprofile-commits
[prev in list] [next in list] [prev in thread] [next in thread]