How should we transition? How about:
1. Set up live protoype Forrest environment (now happening)
- work out remaining configuration issues2. Set up separate Cocoon docs repo(s)
- decide what the repo will include (simply docs and/or tools)
- copy both 2.1 and 2.0 docs and associated files into separate modules/branches/repos. Maintain "old" doc build capability, as currently functioning, in 2.1 and 2.0.
- setup docs build capability for user docs and web site
- add static documentation (built by cocoon-docs repo with Forrest) to both 2.0 and 2.1 repos
- setup mechanism to update (via automated cvs update?) static docs in 2.0 and 2.1 repos. This removes the "burden" of doc-building from code repos. Webapp samples can simply link to static doc files (copied over during webapp build).
3. Remove xdoc, stylesheets, and dtds related to core documentation from 2.0 and 2.1 repos.
4. Consider merging 2.0 and 2.1 into a single trunk (based on Andrew's findings/protype)
Thoughts?
Diana
