Changes between Version 32 and Version 33 of GDAL20Changes


Ignore:
Timestamp:
Jul 3, 2014, 1:39:21 PM (10 years ago)
Author:
Even Rouault
Comment:

mention RFC 46

Legend:

Unmodified
Added
Removed
Modified

  • GDAL20Changes

    v32 v33  
    11= GDAL/OGR 2.0 Changes =
    22
    3 From time to time there has been a suggestion we should at some point have a GDAL/OGR 2.0 release at which point we would relax the normally quite strict desire for backward compatibility in the GDAL/OGR API.  Unification of the GDAL and OGR components of the library is often listed as the main objective of such an overhaul. However, this page is primarily intended to track various other smaller changes that are desirable from a cleanup point of view, but that have been avoided over the last decade to avoid backwards incompatibility.
     3From time to time there has been a suggestion we should at some point have a GDAL/OGR 2.0 release at which point we would relax the normally quite strict desire for backward compatibility in the GDAL/OGR API.  Unification of the GDAL and OGR components of the library is often listed as the main objective of such an overhaul (and it has now been implemented per [http://trac.osgeo.org/gdal/wiki/rfc46_gdal_ogr_unification RFC 46]). However, this page is primarily intended to track various other smaller changes that are desirable from a cleanup point of view, but that have been avoided over the last decade to avoid backwards incompatibility.
    44
    55Please list thoughts on stuff we should revisit at a GDAL/OGR 2.0 release here for future consideration.