Fopdevs, Obviously there is a need for some documention with normal releases. We don't need the design docs in the user releases, but all of the operational material, including the FAQs, is necessary.
If we were to do source and compiled releases, the xml-docs could go into the source release, for generation by the user. Vice versa, the generated html (and pdf docs?) need to be included in binary releases (with the proviso above, that the design docs are not needed.) It looks as though reworking is needed in the build.xml to accommodate these distinctions. How does that sound? Peter Christian Geisert wrote: > Hi, > > The documentation is maintained only in the main branch (does > everybody know this?) > > For the RC I just copied the docs from the main branch and > created the archives manually. For the final release I wanted > to have everything in one place (merge docs from trunk into > maintenance branch) but the problem is that stylebook needs > xerces1 which has been replaced with xerces2. > The question is if we should bring xerces1 back or just copy > the docs over (and tag the main branch with fop-0_20_4-doc) > for the release? > > As Keiron already suggested (I had the same thoughts) I think > we should remove xml-docs (and design) from bin distribution. > I'm not sure about removing html-docs from the src distribution. > > Should we remove the docs completly from the maintenance branch? > > PDF generation of the documentation seems to be broken. > > What is the status of the new FAQ? > > Christian > -- Peter B. West [EMAIL PROTECTED] http://powerup.com.au/~pbwest "Lord, to whom shall we go?" --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
