> * Joshua Slive wrote: > >> Personally, I'm not too concerned with matching docs releases exactly to >> code releases. People can easily use later docs releases with earlier >> versions of 2.0, as long as they pay attention to the "compatibility" >> notes. So I'd say we just release these whenever we feel like it (but >> include the most recent version number to give some idea of time-frame). > > I don't have a strong opinion about it. From the user's view it just may be > more "naturally" to download a docs offline package for a particular > version. (though I'd provide also only the most recent version, of course).
To summarize the POV: a) we ship the HTML documentation together with releases (as we do today) b) additional documentation formats (CHM, PDF, etc.) are generated and published independently from releases and don't come with the actual distribution c) the additional documentation formats are only available for the most recent version (per branch?) If I got this correctly, then I'm +1 :-) > By the way, what do you think about localized HTML offline packages? > (httpd-docs-x.y.z.$lang.tar.gz)? Creation is probably trivial, because we > can adapt concepts/code from the chm creation stuff and build it easily with > ant. Would such packages be useful in any way? Michael Schroepl wrote: > which files would such a localized version contain, > given that most translations don't cover the Apache > documentation to the full extent? Hmmm, I think Michaels point is a very valid one. I'd like to have localized HTML packages too, but up to now I've no idea how to handle this successfully. I know PHP is doing the same, but it's always irritating when you open up the German PDF/CHM version (don't know if they have HTML packages too) and some big parts are in English :-( >> 2. We don't want to give the impression that if you want docs, you need to >> download them separately. > > Good point. That's true. Oh, yes please. Cheers, Erik --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
