[postgis-devel] Bug fixes in trunk NEWS

[Sandro Santilli]

On Wed, Aug 27, 2014 at 12:04:46PM +0200, Sandro Santilli wrote:
> On Wed, Aug 27, 2014 at 05:46:45AM -0400, Paragon Corporation wrote:
> > Strk,
> > 
> > If a bug is fixed in 2.1.4, I agree, we DEFINITELY should not be listing it
> > in 2.2.0.  
> > 
> > There are some bug fixes that truly are bugs, but we deemed too invasive to
> > put in a stable release.  In those cases they would be mentioned in the new
> > minor version (2.2) but they aren't really enhancements.
> > 
> > Those cases should be rare though.
> > 
> > Just my 2 cents.  I don't think we have an official policy on it.  We
> > probably should.
> 
> I agree about the too invasive bugs only being fixed in next minor, but
> this is likely not the case of the 27 currently listed bugfix items:
> https://github.com/postgis/postgis/blob/svn-trunk/NEWS#L64-L96
> 
> Compare with the 2.1 ones:
> https://github.com/postgis/postgis/blob/svn-2.1/NEWS#L13-L20
> 
> +1 on having an official policy

I've removed 28 bugfix items which were already found in other
NEWS sections (as old as 2.0.2!!).

These are the left-over, with inline comments:

  - #2540, Change GUC name for GDAL_DATA to postgis.gdal_datapath

Did the GUC exist in any previous version ? If not this would not
be a bugfix but would be part of the "new feature" of adding such GUC

  - #2777, Raster max extent constraint based upon envelope to behave
           like geometry extent
  - #2822, Use @ operator instead of ST_CoveredBy() for raster
           max extent constraint

Would these two enhancements rather than a bugfix ?
Could they be listed as a single item in the NEWS section ? (they seem
to be conceptually the same enhancement:
speedup of raster extent constraint enforcement).

--strk;

 ()  ASCII ribbon campaign  --  Keep it simple !
 /\  http://strk.keybit.net/rants/ascii_mails.txt