[postgis-devel] Memory Leak (Two Senses)

[Paul Ramsey]

Let's just set the milestone of the bugs we care about to 1.4, and all  
the rest to 1.5

P

On Jan 8, 2009, at 12:24 PM, Mark Cave-Ayland wrote:

> Paul Ramsey wrote:
>
>>> Indeed. I'm inclined to try and keep the LWGEOM disk format  
>>> unchanged from
>>> 1.3 to 1.4 just so that people can just upgrade and hence migrate  
>>> away from
>>> 1.3 to the newer codebase as quickly as possible :)
>> Were you thinking of doing this for 1.4? I figured we were getting
>> close to "fix bugs and start release candidates". Although, now  
>> that I
>> type that, I *really* should force GEOS 3.1 out before we put 1.4  
>> out,
>> so that 1.4 can claim all the new features of GEOS at the same time.
>> P.
>
> Ah okay - I got the impression you were trying to do a lot more work  
> for 1.4 such as the shp2pgsql GUI and the extra lwalgorithm  
> functions, but I'd be quite happy to start to tie up the loose ends  
> and get this ready for general use sooner.
>
> How about creating a page on the wiki called PostGIS14ToDo or  
> similar where we can devise a complete list of outstanding issues  
> for 1.4, listed by developer name? We can then go through and  
> resolve them one-by-one.
>
>
> ATB,
>
> Mark.
>
> -- 
> Mark Cave-Ayland
> Sirius Corporation - The Open Source Experts
> http://www.siriusit.co.uk
> T: +44 870 608 0063
> _______________________________________________
> postgis-devel mailing list
> postgis-devel at postgis.refractions.net
> http://postgis.refractions.net/mailman/listinfo/postgis-devel


--
Paul Ramsey
pramsey at cleverelephant.ca
+1 250 885 0632