forrest-svn mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cross...@apache.org
Subject svn commit: r209816 - /forrest/trunk/etc/publishing_our_site.txt
Date Fri, 08 Jul 2005 15:27:14 GMT
Author: crossley
Date: Fri Jul  8 08:27:13 2005
New Revision: 209816

URL: http://svn.apache.org/viewcvs?rev=209816&view=rev
Log:
Tidy the instructions to use forrestbot to deploy our website docs.
No need to mess with documentation in the branches anymore.

Modified:
    forrest/trunk/etc/publishing_our_site.txt

Modified: forrest/trunk/etc/publishing_our_site.txt
URL: http://svn.apache.org/viewcvs/forrest/trunk/etc/publishing_our_site.txt?rev=209816&r1=209815&r2=209816&view=diff
==============================================================================
--- forrest/trunk/etc/publishing_our_site.txt (original)
+++ forrest/trunk/etc/publishing_our_site.txt Fri Jul  8 08:27:13 2005
@@ -13,28 +13,9 @@
 # Use the forrestbot to build and then deploy to svn.apache.org ...
 
 # forrest -f publish.xml build
-# verify files in build/forrest-[docs|site]
+# verify files in build/forrest-docs
 # forrest -f publish.xml deploy -Ddeploy.svn.commit-message="my commit message"
 
 Now the files are in SVN at forrest/site
 Periodically the real website files are updated from there.
 You do not have to do anything else.
-
------------------------
-
-To publish documentation from a non-trunk branch:
-
-# check out the branch (e.g. svn co https://svn.apache.org/repos/asf/forrest/branches/forrest_07_branch)
-# make sure $FORREST_HOME is set (it uses this to find deploy.svn.settings)
-# Do the steps above within this branch
-
------------------------
-
-To publish documentation from the 0.6 branch:
-
-(this is unique because it does not have split docs/site, but currently we still need to
publish it)
-
-# cd forrest_06_branch
-# forrest -f publish_docs.xml build
-# forrest -f publish_docs.xml deploy -Ddeploy.svn.commit-message="my commit message"
-



Mime
View raw message