[geos-devel] Re: [GEOS] #287: Shouldn't GEOS 3.1 branch be bumped to 3.1.2

[GEOS]

#287: Shouldn't GEOS 3.1 branch be bumped to 3.1.2
------------------------+---------------------------------------------------
 Reporter:  robe        |        Owner:  geos-devel at lists.osgeo.org
     Type:  defect      |       Status:  new                       
 Priority:  trivial     |    Milestone:  3.1.2                     
Component:  Default     |      Version:  3.1.1                     
 Severity:  Unassigned  |   Resolution:                            
 Keywords:              |  
------------------------+---------------------------------------------------
Comment (by robe):

 So I guess I should not be releasing these as part of the PostGIS 1.4.1
 experimental releases.  That was how this became an issue for me.

 I guess to me - at least now, this is a testing concern which I would
 think would be a development concern.

 I was packaging GEOS 3.1 just fixes with 1.4.1 just fixes so that people
 who are having problems fixed by either -- can test out the changes
 without being forced to run a more unstable release.  They could take the
 new GEOS 3.1 (say if they are running 1.3 or 1.4.0 RTM), the new PostGIS
 1.4.1SVN or both. With PostGIS I can tell, with GEOS I can not.

 Now that I can't tell the difference between those running 3.1.1 RTM and
 3.1 stable  non-RTM, this will become a bit confusing from a testing
 standpoint.

-- 
Ticket URL: <http://trac.osgeo.org/geos/ticket/287#comment:2>
GEOS <http://geos.refractions.net/>
GEOS (Geometry Engine - Open Source) is a C++ port of the Java Topology Suite (JTS).