Steven Noels wrote:
Currently, I have a check-out of:
- cocoon_2_0_3_branch - cocoon_2_0_4 tagged files (not a branch!)
^^^^^^
- HEAD
on my machine, but I fail to see how we can consistently decide which branch (or HEAD) should go on the public website.
- news.xml of the HEAD branch contains relevant info
- some docs in the HEAD branch are not pertinent for the public website (non-release-version docs)
- what about the 2_0_3/2_0_4 branch?
- 2_0_4 contains recent changes (at least from Sylvain)
wrong
- 2_0_3 has been the focal point of David's efforts lately
no branch has been created after the 2.0.4 release
Maybe all this might become more clear if we
- isolate docs into their own CVS module (yes, I know this has been suggested before - I believe the complexity and volume of Cocoon doco warrants this, and requires some dedication to sort out where to commit what)
- maintain a branch LIVE_WEBSITE over there?
</Steven>
My bad,
</Steven> -- Steven Noels http://outerthought.org/ Outerthought - Open Source, Java & XML Competence Support Center Read my weblog at http://radio.weblogs.com/0103539/ stevenn at outerthought.org stevenn at apache.org
