[mapserver-dev] Documentation Question

Worth Lutz wal3 at mindspring.com
Thu Jul 21 19:36:52 EDT 2011

As a user lurking on the dev list, my feeling would be for the latest
documentation to only reflect the current state.  I do not like to have to
sort through extraneous information.


Old versions should probably be kept available somewhere.  Much like the
postgreSql and postGis documentation is available for each version.


That would be my preference.  BUT not if it is too much work at the expense
of the great development going on.


Worth Lutz


From: mapserver-dev-bounces at lists.osgeo.org
[mailto:mapserver-dev-bounces at lists.osgeo.org] On Behalf Of Steve Lime
Sent: Thursday, July 21, 2011 12:42 PM
To: mapserver-dev at lists.osgeo.org
Subject: [mapserver-dev] Documentation Question


Question for folks. What's our position regarding multi-version support
within the documentation? For example, there were a number of syntax changes
related to logical expressions in 6.0. We could update the documentation to
reflect 6.0 "as is" with no references to how things worked in older
versions. We could also try to maintain some backwards compatibility so that
the documentation could support all versions. Doing so requires lots of
extra explanation though and makes it harder to maintain. If documentation
is version specific then that would argue for historical documentation to be
made available...




No virus found in this message.
Checked by AVG - www.avg.com
Version: 10.0.1390 / Virus Database: 1518/3778 - Release Date: 07/21/11

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/mapserver-dev/attachments/20110721/6951d1e3/attachment.html

More information about the mapserver-dev mailing list