Changes between Version 3 and Version 4 of Release/3.0/Notes

Timestamp:

01/12/15 06:21:54 (10 years ago)

Author:

jng

Comment:

--

Release/3.0/Notes

@@ -179 +179 @@
    * A different Linux distribution
    
-   Then consider running MapGuide in a [https://www.docker.com/ docker container] that is based on Ubuntu 12.04 or CentOS 6.x. This installation method is not supported and is only for informational purposes.
+   Then consider running MapGuide in a [https://www.docker.com/ docker container] that is based on Ubuntu 12.04 or CentOS 6.x. This installation method is not supported and is only listed here for informational purposes.
  
- * The following FDO providers may not be functional in 64-bit Linux builds of MapGuide
-   * SHP (workaround: Use OGR provider)
+ * The following FDO providers may or may not not be functional in 64-bit Linux builds of MapGuide
+   * SHP (spatial indexing code not working properly, will cause incorrect spatial queries. Workaround: Use OGR provider)
    * MySQL (un-tested, please provide feedback)
    * PostgreSQL (un-tested, please provide feedback)
    * King.Oracle (un-tested, please provide feedback)
    * WFS (un-tested, please provide feedback)
-   * 
+   * WMS (un-tested, please provide feedback)
+
+ * The following FDO providers have been validated in a 64-bit Linux environment by their respective FDO unit test suites (ie. All tests pass). Feedback on these providers in 64-bit Linux still welcome/appreciated:
+   * SDF
+   * SQLite
+   * GDAL
+   * OGR
 
  * Fusion: Bing/VirtualEarth commercial layers may conflict with Google layers if they are both specified in a Flexible Layout. If you have a Bing/VirtualEarth layer as the default, switching to a Google layer in your Fusion application will cause the Google layer to be displaced and vice versa.