Steven Noels wrote:
(follow up to cocoon-docs please)
On 24/03/2003 7:31 Steven Noels wrote:
In order to get one little step closer to the 'new' document infrastructure, many of us seek clarity whether we should move docs to a separate CVS module or not. The benefits and downfalls are largely known, so let's vote on this and get this issue cleared.
My own personal bias: don't forget the different Cocoon _versions_ are now stored in separate modules, too.
Please cast your vote:
results so far:
[ ] creation of cocoon-docs module: morrijr, shannon, stefano, bdelacretaz
not sure because of comments: sylvain
In order to remove the "not sure" : I'm firmly +1 for a cocoon-docs module.
The comments were about the transition period before the new doc system is fully operational, in which we should take care to still be able to build the "old" docs to avoid a "no-docs" period.
We are already able to build the docs using forrest. Try the following:
cvs checkout cocoon-2.1 cvs checkout xml-forrest cd xml-forrest ./build.sh dist-shbat cd ../cocoon-2.1 ./build.sh forrest
they key is to have the two cvs modules living side by side and preparing the shbat dist (what a stupid name, anyway) first.
Stefano.
