On Wed, 2003-11-26 at 17:59, Brett Porter wrote: > > 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.
I've always liked this idea and actually tried to do it in Turbine but nobody went for it. I think it clearly separates the docs and we can actually give out perms to doco folk (if we ever get some :-)) and not worry about them punching the core. +1 > > 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 > -- jvz. Jason van Zyl [EMAIL PROTECTED] http://tambora.zenplex.org In short, man creates for himself a new religion of a rational and technical order to justify his work and to be justified in it. -- Jacques Ellul, The Technological Society --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
