On Saturday 13 March 2004 21:34, Farr, Aaron wrote: > * javadocs should be published for only the latest STABLE release unless > otherwise noted in the link description
This is a big management issue, and as Stephen suggests I also think that ALL DOCS require to be hard versioned on the website, and that the default symlinks to the latest released version, but all older versions should also be available. I suggest that we put in place a system, where documentation is tagged at every release with the Version ( ex, V1_3 ), and if it needs update, it is branched and updated in the CVS branch. That means that HEAD is always ahead of the release, just like code, and can be managed from source point of view. And when generating the site, we need to pull out the properly tagged version (NOT HEAD) and generate into a directory of that version, and then do the symlink. Complicated, yes, somewhat... These are the kind of stuff that Maven should help us with. > * we need to official adopt a versioning scheme and begin enforcing it > I think the APR rules make sense. We can work on a way to automate it or > whatever, I don't care. We just need consistency. I agree 148.3% !!! APR have probably nailed this down (I dare to say without checking), so let's not re-invent the wheel. Niclas -- +---------//-------------------+ | http://www.bali.ac | | http://niclas.hedhman.org | +------//----------------------+ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
