> I would say the normal site should point at the current > release docs and then use your scheme to point at any number > of desired branches.
I agree. This was the original plan I think. I like the way Cactus does it too, in the top right nav link. But in the interim, we just keep doing what we do - but publish from the branch. Vincent's proposal is good. I especially like that you only have one version in CVS and publish to a new location on the web site. I don't like the maven-plugins solution of copying directories around for releases. The only problem was there needed to be exceptions for some of the user supplied xdoc, as opposed to the generated reports. Ie, you want the version to say 1.0-rc2, and you want the RC2 javadoc and reports, you want the RC2 installation instructions, but you want to be able to update the home page, FAQ, navigation, articles, etc mid release. Any thoughts on how we can do this? I still think an independent site module that contains those things is the best way, but it needs to integrate such that you get the current release # in the top bar and the navigation has the correct reports links. Another option is to branch the xdoc directory from the last release whenver making edits in CVS and republish from there, but that could get hairy... Also, this policy needs to work for the plugins site too, and something other users can utilise. Cheers, Brett
