cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Reinhard Poetz <reinh...@apache.org>
Subject Re: FAQ dcoument
Date Sun, 06 Jan 2008 12:51:25 GMT
Vadim Gritsenko wrote:
> On Jan 5, 2008, at 9:53 AM, hepabolu wrote:
> 
>> Grzegorz Kossakowski said the following on 5/1/08 13:51:
>>> Hi,
>>> I added[1] FAQ-entry for the subject of much controversy among Cocoon 
>>> community. Now I wonder how to
>>> get it published, I found old document aggregating all FAQ entries 
>>> but it doesn't work ATM. Before I
>>> go and fix it I would like to ask your opinion on separating FAQs for 
>>> Cocoon 2.1 and Cocoon 2.2.
>>> Obviously, some entries addressed to 2.2 version has no value for 2.1 
>>> user. If we are going to
>>> separate FAQ documents, how we will mark to which version particular 
>>> entries are addressed? Using
>>> tags or some other mechanism?
>>> My personal opinion is that tags will be the most convenient choice.
>>> [1] http://cocoon.zones.apache.org/daisy/cdocs/1425.html
>>> [2] http://cocoon.zones.apache.org/daisy/documentation/856.html
>>
>> The regular Daisy approach is to create a branch for each version. 
>> That way you can answer the same FAQ different for each version. I'm 
>> not sure if you can batch move documents to a specific branch.
> 
> IMHO there is no much potential for shared FAQs with two different 
> answers for each version. I think it's a better approach to have unique 
> FAQ document per version, meaning for 2.2 we should start from scratch.

+1

additionally I've never tested if the Daisy exporter works correctly with 
references to branched documents. If we ever need this in the future, we will 
have to try it out before.

-- 
Reinhard Pötz                            Managing Director, {Indoqa} GmbH
                           http://www.indoqa.com/en/people/reinhard.poetz/

Member of the Apache Software Foundation
Apache Cocoon Committer, PMC member, PMC Chair        reinhard@apache.org
_________________________________________________________________________

Mime
View raw message