[postgis-devel] [PostGIS] #1802: Ensure interruptability of long-running calls

[PostGIS]

#1802: Ensure interruptability of long-running calls
---------------------+------------------------------------------------------
 Reporter:  strk     |       Owner:  strk         
     Type:  task     |      Status:  new          
 Priority:  medium   |   Milestone:  PostGIS 2.0.1
Component:  postgis  |     Version:  2.0.x        
 Keywords:           |  
---------------------+------------------------------------------------------

Comment(by mcayland):

 The part about the transform_geom() function was an aside in the last
 paragraph of that message - it was not part of the patch at that time, and
 does nothing to detract from your clear statement that the 1.0 branch was
 for bugfixes only.

 The aim of a stable branch is to introduce only the *minimal* changes
 required in order to produce correct functionality before the new point
 release - anything else is a feature. If we do this, where do we stop?
 Paul has some ideas about internally indexing large geometries - do we put
 that in 2.0.1? What about some of Bborie's changes, where he waited until
 we branched before committing them as per our normal development process?
 Should we backport those too?

 And now I see that rather than wait to discuss this, you've just gone
 ahead and committed anyway. I repeat what I said before - this is not fair
 on the other developers. I'm sorry, but it comes across that you've
 committed the code to the stable branch to meet either a personal/business
 requirement in violation of our normal guidelines, and this is completely
 unacceptable.

 +1 for reverting for this commit.

-- 
Ticket URL: <http://trac.osgeo.org/postgis/ticket/1802#comment:20>
PostGIS <http://trac.osgeo.org/postgis/>
The PostGIS Trac is used for bug, enhancement & task tracking, a user and developer wiki, and a view into the subversion code repository of PostGIS project.