Add clarifications from Jeff Turner & Christian Geisert regarding publication process.

git-svn-id: https://svn.apache.org/repos/asf/xmlgraphics/fop/trunk@195771 13f79535-47bb-0310-9956-ffa450edef68

diff --git a/src/documentation/README b/src/documentation/README
index a4e30b11c2cc2bc395b2e8331e652c2881d768e6..c3ccc116680dd73e78db773e83551a8b523aed19 100644 (file)
--- a/src/documentation/README
+++ b/src/documentation/README
@@ -1,3 +1,5 @@
+$Id$
+
 To update the FOP website:
 
 Background
@@ -35,15 +37,23 @@ Step-by-Step Instructions
 
 Notes
 ---------
- 1. Per Jeff Turner, the downstream process of publishing our web site is as
-    follows:
-    - Committers commit generated docs to xml-site/targets/{project}
-    - Every X hours, a script updates /www/xml.apache.org/ or wherever on
-      the live site, from CVS.
- 2. Per Jeff Turner, the FOP website is being regenerated (from the contents
-    of xml-site/targets/fop) by Forrest every hour.
+ 1. Per information from Jeff Turner & Christian Geisert, the downstream
+    process of publishing our web site is as follows:
+    - Committers commit generated docs to xml-site/targets/fop
+    - Every 6 hours (midnight, 6am, noon, 6pm Pacific time), a script (which is
+      maintained by Sam Ruby) updates the FOP website:
+      - soucre: icarus (cvs.apache.org), specifically from
+        /home/cvs/xml-site/targets/fop.
+      - target: daedalus (xml.apache.org)
+ 2. Per Jeff Turner, the contents of the FOP website (but not the web site
+    itself) are being regenerated by Forrest every hour.
+    This process actually checks out the contents of xml-fop/src/documentation
+    from CVS and builds the web-site contents with the latest Forrest.
+    This process has no relation to what is in xml-site/targets/fop.
     See http://forrestbot.cocoondev.org/site/xml-fop for the contents.
     Although we found this interesting (especially wondering how they got around
     the headless server problem), it doesn't change our workflow above, because
     we don't know where, at the filesystem level, these files exist, so we have
     no way of copying them to xml-site/targets/fop.
+
+Last Line of $RCSfile$
\ No newline at end of file