vmote       2002/12/14 10:11:24

  Modified:    src/documentation README
  Log:
  Add clarifications from Jeff Turner & Christian Geisert regarding publication 
process.
  
  Revision  Changes    Path
  1.3       +17 -7     xml-fop/src/documentation/README
  
  Index: README
  ===================================================================
  RCS file: /home/cvs/xml-fop/src/documentation/README,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- README    11 Dec 2002 19:06:38 -0000      1.2
  +++ README    14 Dec 2002 18:11:24 -0000      1.3
  @@ -1,3 +1,5 @@
  +$Id$
  +
   To update the FOP website:
   
   Background
  @@ -35,15 +37,23 @@
   
   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
  
  
  

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to