Vincent Massol wrote:
While I agree with the goal, I think it's important that users *know* they're browsing the docs for the current version in CVS, and not for the latest stable release most are probably using.Hi,So far, the Cactus web site has always been displaying the documentation for the latest released version. However, we tried to update it with news, changes, etc which forces us to apply the changes both to the released branch and to the HEAD. I've tried it for a few months and I now find this a bit of a pain... I'd like to propose to now display the documentation for the HEAD on the web site (i.e. 1.5dev ATM) *BUT* to keep a link to the documentation for the last released version online too. What do you think?
Struts is doing this quite nicely. They have sections with documentation for the "Latest Stable Release", "Latest Beta Release" and "Nightly Build".
I'm not quite sure how they automate the website build... using branches/tags in CVS seems most elegant but would require a pretty nifty Ant script. Also, website generation will need to be separate from doc-generation.
--
Christopher Lenz
/=/ cmlenz at gmx.de
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
