svn commit: r606261 - /commons/proper/commons-build/trunk/xdocs/releases/release.xml

[ra...@apache.org]

Author: rahul
Date: Fri Dec 21 10:01:40 2007
New Revision: 606261

URL: http://svn.apache.org/viewvc?rev=606261&view=rev
Log:
Update the section on publishing changes to the Commons website.

Modified:
    commons/proper/commons-build/trunk/xdocs/releases/release.xml

Modified: commons/proper/commons-build/trunk/xdocs/releases/release.xml
URL: http://svn.apache.org/viewvc/commons/proper/commons-build/trunk/xdocs/releases/release.xml?rev=606261&r1=606260&r2=606261&view=diff
==============================================================================
--- commons/proper/commons-build/trunk/xdocs/releases/release.xml (original)
+++ commons/proper/commons-build/trunk/xdocs/releases/release.xml Fri Dec 21 10:01:40 2007
@@ -477,8 +477,7 @@
     <p>
     If you are creating a component site for the first time, then you will need to
     update file commons-build/menus/components-items.ent in subversion and publish
-    the updated commons site. In all other circumstances, you can skip this step as
-    there is nothing in the commons website that needs updating.
+    the updated commons site.
     </p>
     <p>
     To update the commons site:
@@ -486,8 +485,13 @@
     <li>check out the entire commons/trunks-proper directory (the build process
         needs all the other components checked out).</li>
     <li>cd commons/trunks-proper/commons-build</li>
+    <li>edit downloads/downloads.xml as necessary</li>
     <li>maven site:generate</li>
+    <li>ant -f build-downloads.xml</li>
     <li>maven -Dmaven.username=yourapacheid site:deploy</li>
+    <li><strong>check that the cgi scripts in the deployed site on
+        people.apache.org are executable</strong> (if not chmod 775 the cgi
+        scripts)</li>
     </ul>
     Note that the website is actually served from another machine, so it may take a
     few hours until those changes are transferred to the actual webserver host machine.