[mapserver-dev] Documentation updates

[Steve Lime]

But having those flags is also nice to have. It's very convenient to be able to look at
one document and say "if I need feature X I need to upgrade to version Y). Otherwise
you have to dig through difference versions of the same document and hope to discover
when something was added or changed.

Steve

>>> On 3/6/2008 at 7:55 AM, in message <47CFF7DD.7060804 at mapgears.com>, Daniel
Morissette <dmorissette at mapgears.com> wrote:
> Steve Lime wrote:
>> Personally I'd favor one set of docs, with notes where applicable about 
> version specific issues. If there are
>> big changes in one area then perhaps it would be necessary to have a version 
> specific document but that's
>> relatively rare. Most things tend to be quite stable. Having a single 
> "MapFile Reference" would be a lot 
>> easier to maintain. Just a thought...
>> 
> 
> Even with versioning, you'd still have a single "Mapfile Reference" doc 
> to maintain... the only difference is that at release time you freeze 
> and branch the current mapfile ref for the release and the trunk version 
> can be edited to contain new features for the next release.
> 
> That's as easy as it gets in my opinion. That's also the way things used 
> to work in the "blue" site and I think this something we lost when we 
> migrated to the Plone site. Having to flag specific paragraphs from the 
> docs with versions to which they apply is a mess to read and to maintain 
> in my opinion.
> 
> Daniel