[postgis-devel] PSC Vote: Are we ready for a 2.3.7 and 2.4.4 in about a week?
Regina Obe
lr at pcorp.us
Fri Mar 23 08:48:20 PDT 2018
Scanning thru the News of 2.3 and 2.4 branches, looks like we've got quite a
few bug fixes.
Is everyone okay if I do a release in about a week. With a soft-launch
early next week (I'll package give people the links, before I deploy to
official production location)
For reference
2.4.4 has (I'd change the #3946 to compiles but doesn't regress or perhaps
we just shouldnt mention it at all :) )
* Bug fixes *
- #3978, Fix KNN when upgrading from 2.1 or older (Sandro Santilli)
- #4004, Avoid memory exhaustion when building a btree index (Edmund
Horner)
- #4003, lwpoly_construct_circle: Avoid division by zero (Raúl Marín
Rodríguez)
- #4020, Casting from box3d to geometry now returns correctly connected
PolyhedralSurface (Matthias Bay)
- #3942, geojson: Do not include private header for json-c >= 0.13
(Björn Esser)
- #4025, Incorrect answers for temporally "amost overlapping" ranges
- #4017, lwgeom lexer memory corruption (Peter E)
- #4052, schema qualify several functions in geography
* Enhancements *
- #3992, Use PKG_PROG_PKG_CONFIG macro from pkg.m4 to detect pkg-config
(Bas Couwenberg)
- #3946, Support for PgSQL 11 (Paul Ramsey)
News, we have the following for 2.3.7
- #3978, Fix KNN when upgrading from 2.1 or older (Sandro Santilli)
- #4003, lwpoly_construct_circle: Avoid division by zero (Raúl Marín
Rodríguez)
- #4020, Casting from box3d to geometry now returns correctly connected
PolyhedralSurface (Matthias Bay)
- #4025, Incorrect answers for temporally "amost overlapping" ranges
- #4017, lwgeom lexer memory corruption (Peter E)
- #4052, schema qualify several functions in geography
More information about the postgis-devel
mailing list