[postgis-devel] Bug fixes in trunk NEWS

[Paul Ramsey]

Agreed that bug fixes should be called out in patch release NEWS, but not in trunk NEWS.

P.

-- 
Paul Ramsey
http://cleverelephant.ca
http://postgis.net

On August 27, 2014 at 8:55:53 AM, Sandro Santilli (strk at keybit.net) wrote:

On Wed, Aug 27, 2014 at 07:20:12AM -0400, Greg Troxel wrote:  

> NEWS is supposed to be for changes that a user would care about. So  
> bugfixes are generally not notable, unless they are for something so  
> serious that results would have been wrong before, or some workaround  
> can be stopped.  

Yep, but bugfixes are usually all visible.  

> As for previous branches, it's an interesting question which version  
> NEWS is relative to. It's a fair policy that NEWS on trunk is relative  
> to the most recent release of the current stable branch. Which means  
> that items added to 2.x.y on the 2.x branch should also be added to NEWS  
> on trunk under 2.x (as part of the merge/backport), so that NEWS on  
> 2.x+1.0 looks like 2.x.y's NEWS plus the 2.x+1.0 entry (with nothing  
> missing).  

I've just added the missing section for 2.0.5, 2.0.6 and 2.1.3  
releases in the NEWS file of trunk. New sections shall be added  
as new releases are published.  

One day we'll need to split between old news and new news...  

grep ^PostGIS NEWS | wc -l # 63 and counting  

Keeping users informed since 2001/05/25 ! :)  

--strk;  
_______________________________________________  
postgis-devel mailing list  
postgis-devel at lists.osgeo.org  
http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-devel  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-devel/attachments/20140827/c8650a5a/attachment.html>