Return-Path: Delivered-To: apmail-xml-cocoon-docs-archive@xml.apache.org Received: (qmail 43810 invoked by uid 500); 18 Oct 2002 11:21:45 -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 43788 invoked from network); 18 Oct 2002 11:21:44 -0000 Received: from fep02.tuttopmi.it (HELO fep02-svc.flexmail.it) (212.131.248.101) by daedalus.apache.org with SMTP; 18 Oct 2002 11:21:44 -0000 Received: from apache.org ([80.204.154.181]) by fep02-svc.flexmail.it (InterMail vM.5.01.05.09 201-253-122-126-109-20020611) with ESMTP id <20021018112143.SRXF21529.fep02-svc.flexmail.it@apache.org> for ; Fri, 18 Oct 2002 13:21:43 +0200 Message-ID: <3DAFEE89.3080905@apache.org> Date: Fri, 18 Oct 2002 13:20:41 +0200 From: Nicola Ken Barozzi Reply-To: nicolaken@apache.org Organization: Apache Software Foundation User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826 X-Accept-Language: en-us, en MIME-Version: 1.0 To: cocoon-docs@xml.apache.org Subject: Re: Keeping website docs in sync with *released* version? (was...starting to write it on the wiki?) References: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Status: O X-Status: X-Keywords: Diana Shannon wrote: > > On Thursday, October 17, 2002, at 06:19 AM, Bertrand Delacretaz wrote: ... >> a) Default version of website docs stays frozen as it was when the last >> release was done (except the "news" pages). > > > I disagree. Why should it be frozen? To make it easier on committers? I > think this might discourage patching and updating docs. > >> b) Publish the CVS versions of the docs on alternate path >> (xml.apache.org/cocoon/work-in-progress > > What does works-in-progress refer to? The code or the docs? Both; usually WIP docs are related to WIP functionality, anyway it's a simplification. Over @the Ant dev list, there have been already discussions about users complaining they wanted the "release" version of the docs, while others wanted only CVS version. Personally, I'm totally convinced we need both. Or keep the CVS version up front and link to the releases versions, or the opposite. But having WIP on the main page is really bad... >> or xml.apache.org/cocoon-cvs) with a >> suitable warning on all pages ("this relates to the unstable CVS >> version blah >> blah..."). > > > Warnings already exist. Some docs with 2.1 content still lack them, though. > > How would you implement the build? Isn't it better to add this > functionality to Forrest first? +1, as I suggested -- Nicola Ken Barozzi nicolaken@apache.org - verba volant, scripta manent - (discussions get forgotten, just code remains) ---------------------------------------------------------------------