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


Ignore:
Timestamp:
Jan 12, 2015, 6:16:06 AM (9 years ago)
Author:
jng
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • Release/3.0/Notes

    v2 v3  
    3030   * Size: TBD bytes
    3131   * md5: TBD
     32Ubuntu 12.04 install script (64-bit):
     33 * TBA
     34   * Size: TBD bytes
     35   * md5: TBD
    3236CentOS 6.x install script (32-bit):
     37 * TBA
     38   * Size: TBD bytes
     39   * md5: TBD
     40CentOS 6.x install script (64-bit):
    3341 * TBA
    3442   * Size: TBD bytes
    … …  
    9098=== MapGuide ===
    9199
     100 * 64-bit Linux support (available in 3.0 as a preview release)
    92101 * Various deprecated APIs have been removed [http://trac.osgeo.org/mapguide/wiki/MapGuideRfc139 MapGuide RFC 139]
    93102 * Additional Convenience APIs [http://trac.osgeo.org/mapguide/wiki/MapGuideRfc143 MapGuide RFC 143]
    … …  
    122131This release is built against the FDO trunk (SVN rev 7169)
    123132
     133Key items in FDO 4.0 of benefit to MapGuide include:
     134
     135 * SHP provider implements [http://trac.osgeo.org/fdo/wiki/FDORfc23 FDO RFC 23] (fixes #175)
     136 * An OGR Provider with enhanced FDO expression capabilities and many bug fixes [http://trac.osgeo.org/fdo/wiki/FDORfc69 FDO RFC 69]
     137
    124138== Installer notes ==
    125139
    … …  
    159173
    160174== Known Issues ==
     175
     176 * Using the Linux builds of MapGuide on distributions they were not built for is not supported. If you want to run MapGuide on:
     177   * Versions of Ubuntu newer than 12.04
     178   * CentOS 7 or higher
     179   * A different Linux distribution
     180   
     181   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.
     182 
     183 * The following FDO providers may not be functional in 64-bit Linux builds of MapGuide
     184   * SHP (workaround: Use OGR provider)
     185   * MySQL (un-tested, please provide feedback)
     186   * PostgreSQL (un-tested, please provide feedback)
     187   * King.Oracle (un-tested, please provide feedback)
     188   * WFS (un-tested, please provide feedback)
     189   *
    161190
    162191 * 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.