[Plplot-cvs] SF.net SVN: plplot:[11346] trunk/README.Release_Manager_Cookbook

[<ai...@us...>]

Revision: 11346
          http://plplot.svn.sourceforge.net/plplot/?rev=11346&view=rev
Author:   airwin
Date:     2010-11-22 07:39:17 +0000 (Mon, 22 Nov 2010)

Log Message:
-----------
Tweak directions to set PLplot release version number of
doxygen-generated documentation.

Also, tweak directions to account for the important change in
scripts/generate_website.sh which copies all files under svn control
(including all local changes to those files) from the source tree that
includes that script.  This change, means for example, that as a
matter of convenience the release manager (or anybody else) does not
have to commit local changes in order to generate and test the
website based on those local changes.

Modified Paths:
--------------
    trunk/README.Release_Manager_Cookbook

Modified: trunk/README.Release_Manager_Cookbook
===================================================================
--- trunk/README.Release_Manager_Cookbook	2010-11-22 01:32:44 UTC (rev 11345)
+++ trunk/README.Release_Manager_Cookbook	2010-11-22 07:39:17 UTC (rev 11346)
@@ -92,16 +92,23 @@
 are generated.  The list also automatically controls what examples-related
 files are copied to the website.
 
-Update the project web page, including the examples: edit www/examples.php
-to reflect the forthcoming release number and any changes to the examples
-themselves (i.e. pages added or removed from an existing example or entirely
-new examples).
+Update the project web page, including the examples: edit
+www/examples.php to reflect the forthcoming release version number and
+any changes to the examples themselves (i.e. pages added or removed
+from an existing example or entirely new examples).
 
-svn commit the updated pages since the script below downloads directly
-from the svn repository rather than working with any local files.
+Edit PROJECT_NUMBER in doc/Doxyfile.in to reflect the release
+version number.
 
-Run (on a Linux host that is capable of building the documentation)
+The above changes may be committed now or later in the release process
+(see "Using svn, commit the above changes" below) since the
+script, scripts/generate_website.sh uses the local source
+tree where that script resides (including all local changes)
+as the source tree for generating the website.)
 
+Run (on a Linux host that is capable of building the documentation
+for the source tree that has all local changes)
+
 scripts/generate_website.sh
 
 with no arguments.  The script asks you four questions, gives you a chance


This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.