Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Received-SPF: neutral (asf.osuosl.org: local policy)
Message-ID: <4371DDBF.40908@apache.org>
Date: Wed, 09 Nov 2005 11:30:07 +0000
From: Ross Gardler <rgardler@apache.org>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
MIME-Version: 1.0
To: dev@cocoon.apache.org
Subject: Re: [Vote] Releasing 2.1.8 tomorrow
References: <437083F2.1030004@apache.org>
 <20051109003703.GA8559@igg.indexgeo.com.au>
 <683e5898e6f48d7d96a5df5a7ac55214@apache.org>
 <20051109033549.GA9072@igg.indexgeo.com.au> <4371D494.3060506@apache.org>
In-Reply-To: <4371D494.3060506@apache.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Ross Gardler wrote:
> David Crossley wrote:
> 
>> Bertrand Delacretaz wrote:
>>
>>> David Crossley a ?crit :
>>>
>>>> ...As i warned a long time ago, the re-arrangement of
>>>> documentation should not have been done until the
>>>> 2.2 release...
>>>
>>>
>>> Fully agreed, staying with the old docs for 2.1.8 seems much easier, 
>>> and 2.2 is a good time to make a transition on the docs.
>>>
>>>
>>>> ...If people are not going to help fix the new Daisy-based
>>>> documentation for this release, then we we need to
>>>> repair the old documentation building system, e.g. the
>>>> index.xml file seems to be missing and various other
>>>> source files have been deleted...
>>>
>>>
>>> Could we do the release and regenerate only the index and news pages?
>>> I don't think there have been much changes to other parts of the 
>>> "old" docs.
>>>
>>> I'm strongly for releasing 2.1.8 with the "old" docs and take our 
>>> time to improve them for 2.2.
>>
>>
>>
>> Good idea, i was wondering about that as a workaround.
>> We can easily update the complete top-level docs, same
>> as before.
>> http://wiki.apache.org/cocoon/CocoonWebsiteUpdate
> 
> 
> You can also add entries to the locationmap in the daisy-to-docs module 
> that will retrieve the relevant content from SVN. That is, documents you 
> want to come from the old SVN files would have an entry pointing at 
> http://svn.a.o/... instead of at daisy. When the site is built Forrest 
> will retrieve the content from the relevant place.

Ahhh... "slight" problem with that. The Daisy plugin does not currently 
support content from alternative locations, it used to until I fixed the 
URLspace issues for Cocoon, and I've not got around to making that work 
again, sorry.

The above will be possible soon, but not sure when I'll have the time to 
tackle it. Probably better to build those pages by hand as you suggest, 
it's only a handful.

Ross

Ross