Blug, I was hoping the memory leak in the preparedgeometry work would be gone before we got 3.1 out the door. I'm afraid that the 1.3.x series of PostGIS has a detection in it that will turn on the prepared optimization if it detects GEOS 3.1, which would be bad if GEOS 3.1 has a broken prepared implementation. :(
Rock meet hard place. P On Fri, Aug 1, 2008 at 4:27 PM, Mateusz Loskot <[EMAIL PROTECTED]> wrote: > Folks, Dear PSC, > > Recently, new feature [1] to the public C API has been applied. > It was on request from QGIS folks. They are are porting QGIS to GEOS C API > and use Polygonizer::getCutEdges which was not exposed. > Now, it seems important to synchronize release dates of QGIS 1.0.0 > with new release of GEOS - the one that will include the new features. > > First, I thought GEOS 3.0.1 (with #195 fix included) should make the job, > but then I reminded that the fix changes public api, so it applies more to > GEOS 3.1.0. > > IMO, would not be a bad idea to release 3.1.0. > It's been 8 months since 3.0.0 and a bunch of fixes have > been applied [3]. > > > What do you think? > > > [1] http://trac.osgeo.org/geos/ticket/195 > [2] http://lists.osgeo.org/pipermail/qgis-developer/2008-July/004529.html > [3] > http://trac.osgeo.org/geos/timeline?from=08%2F01%2F08&daysback=225&changeset=on > > Best regards > -- > Mateusz Loskot, http://mateusz.loskot.net > Charter Member of OSGeo, http://osgeo.org > _______________________________________________ > geos-devel mailing list > geos-devel@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/geos-devel > _______________________________________________ geos-devel mailing list geos-devel@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/geos-devel
