> I thought we should at least merge the xdocs folder in the trunk, > reorganize it and merge something back to the 2.3 branch.
> Most docs have a 2_1 suffix, only few 2_2, none 2_3. I don't like too > much the suffix solution to documentation versioning. My proposal would > be to remove the version name from the filenames and eventually backup > old versions in subfolders. The last generate site should document the > last official release. You know, we actually have discussed all of this and have the plan. The only thing missing has been someone doing the work with Ant. Danny was going to do it initially, and he's had no time. > I'd like we reach a consensus on what to do so I can updated the > http://issues.apache.org/jira/browse/JAMES-432 We deliberately setup the site project, and should should move the web site xdocs to there. We are supposed to split the site docs from the version specific project docs, so that each release would have its own place on the site. For example, you just merged it back into trunk. So how does that in any way help with the next release? If necessary, I suppose that until we fix the Ant scripts, we could define an svn:external reference to bring the site trunk into the build tree. > IIRC I read Noel being contrary to maven generated sites. Absolutely! You can pretty much put it down as maven in general, and most especially maven generated sites. --- Noel --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
