Right. There has always been one version of the doc per release online and would continue to be done the same. If you ship it with the release there is still a version of the help for every release. That's true if you contend for a doc fix that could only go into one release and not the next. For example, you could document a work-around in 2.6, fix the problem in 3.0, and now the 3.0 documentation needs none of the 2.6 wording. So you're still building separate versions when shipped with the releases.
Thanks Troy -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Britt Fitch Sent: Friday, September 14, 2012 3:59 PM To: [email protected] Subject: Re: Apache Confluence wiki for documentation? I also like to have documentation shipped with the code. If documentation is web only then there needs to be multiple versions maintained anyway, otherwise you force everyone to update to have support. Britt On Sep 14, 2012, at 10:26 AM, Jörn Kottmann <[email protected]> wrote: > On 09/14/2012 04:19 PM, Masanz, James J. wrote: >> I also prefer to not distribute the documentation with the release. > > I actually prefer to have the documentation included in the > distribution, because then I can always easily access the > documentation which matches the version I am working with and do not > have to go somewhere to find it. > > Jörn
