Return-Path: Delivered-To: apmail-xml-cocoon-docs-archive@xml.apache.org Received: (qmail 98679 invoked by uid 500); 21 Mar 2003 04:35:55 -0000 Mailing-List: contact cocoon-docs-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-docs@xml.apache.org Delivered-To: mailing list cocoon-docs@xml.apache.org Received: (qmail 98663 invoked from network); 21 Mar 2003 04:35:55 -0000 Received: from mailgate2.sover.net (209.198.87.64) by daedalus.apache.org with SMTP; 21 Mar 2003 04:35:55 -0000 Received: from localhost (dialup4028.wnskvtao.sover.net [216.114.175.219]) by mailgate2.sover.net (8.11.6/8.11.6) with ESMTP id h2L4a3D07479 for ; Thu, 20 Mar 2003 23:36:03 -0500 (EST) Date: Thu, 20 Mar 2003 23:31:41 -0500 Subject: Re: Migration to Forrest Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v482) From: Diana Shannon To: cocoon-docs@xml.apache.org Content-Transfer-Encoding: 7bit In-Reply-To: Message-Id: <03BF3C43-5B56-11D7-8A27-0030653FE818@apache.org> X-Mailer: Apple Mail (2.482) X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N On Thursday, March 20, 2003, at 03:53 PM, Stephan Michels wrote: > I tried to solve some issue for releasing 2.1. So I took some time > to integrate Forrest into the current build system. I create > successfully the docs, except some links. Fabulous! Thanks for taking the time to help on this! > See http://vern.chem.tu-berlin.de/~stephan/cocoon/index.html > > But for me there are some issue unresolved: > > 1. Should Cocoon any longer produce his own docs? This mean > that we must include stuff from forrest. I don't think the repos need build capability. Perhaps we should consider making pre-built html docs snapshots available? Not sure about including the prebuilt docs in each cvs, but that's probably what users would expect. > 2. Which skin should be used? I'd vote for Forrest. We can always make our own down the road. > 3. Can we use something like a forrest cent? I'll defer to Nicola Ken on this. > 4. I cut the build.xml into several fragments to increase the clearness. I'm not sure what you mean here, but I'll check it out, once you commit it somewhere. Diana