On Feb 8, 2010, at 8:12 PM, Greg Coats wrote: > otherwise people will have to wait until GDAL 1.7.2 before being able to use > it.
I don't see the relaxing of this as any reason to hold up the release. In fact, one could argue this is a new feature just as easily and should be targeted at 1.8. A search found http://trac.osgeo.org/gdal/ticket/2801 and http://trac.osgeo.org/gdal/changeset/18657 which was in trunk, with no effort to target or backport this to 1.7 at this time. > This was not immediately obvious because all of the files in the RC have the > same date created and date modified, today. A few seconds reading 'svn log' or 'svn blame' output and looking at http://trac.osgeo.org/gdal/log/trunk/gdal/frmts/jp2kak/jp2kakdataset.cpp can show you what you are looking for. It is important to bring up your pet issue(s) *before* the release candidate is made, and not demand that we stop everything and turn the boat around afterward. If you have something that is important to you, you should follow it, ticket it, and watch the code you care about during the period between releases. Alternatively, filing tickets with patches and test cases attached will ensure quick resolution of your issue. Howard_______________________________________________ gdal-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/gdal-dev
