[postgis-devel] Bug fixes in trunk NEWS

[Paragon Corporation]

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.




Thanks,
Regina

-----Original Message-----
From: postgis-devel-bounces at lists.osgeo.org
[mailto:postgis-devel-bounces at lists.osgeo.org] On Behalf Of Sandro Santilli
Sent: Wednesday, August 27, 2014 5:13 AM
To: postgis-devel at lists.osgeo.org
Subject: [postgis-devel] Bug fixes in trunk NEWS

Do bugfixes really belong in the NEWS file for trunk ?
As trunk is bound to next minor version, being a feature release, shouldn't
it only contain new features and enhancements instead ?

The rationale for that is that any bugfix should end up in a bugfix release
of the previous version, like in our case all bugfixes would be in 2.1.4.

Or are we duplicating bugfix notices in both places ?

My vote would go to ensuring any bugfix enters the latest stable branch and
gets noticed in there, and to cut a bugfix release before publishing the
next feature release.

--strk; 

 ()  ASCII ribbon campaign  --  Keep it simple !
 /\  http://strk.keybit.net/rants/ascii_mails.txt
_______________________________________________
postgis-devel mailing list
postgis-devel at lists.osgeo.org
http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-devel