[postgis-devel] Call for 1.5.2 release

[Paul Ramsey]

Indeed it should, trunk's just the place for a new
needs-to-be-tested-and-worked-on version of the GUI.

On Tue, Aug 10, 2010 at 4:52 PM, Paragon Corporation <lr at pcorp.us> wrote:
> Yes we should stick with the old one.  The new one I agree is such a major
> change that it really needs more testing.
>
> I haven't compiled PostGIS 1.5 in while (and haven't yet so don't know if I
> will run into issues).  I assume not since Mark made a build for Windows.
>
> I didn't notice that Mark L had moved his changes from spike to 1.5.
>
> But -- why arent' these changes in PostGIS 2.0.  The 2.0 version looks like
> the old 1.5 unlesss I am mistaken, and I don't see any migrate there.
> Shouldn't that one have the new changes?
>
> Thanks,
> Regina
>
> -----Original Message-----
> From: postgis-devel-bounces at postgis.refractions.net
> [mailto:postgis-devel-bounces at postgis.refractions.net] On Behalf Of Paul
> Ramsey
> Sent: Tuesday, August 10, 2010 7:39 PM
> To: PostGIS Development Discussion
> Subject: Re: [postgis-devel] Call for 1.5.2 release
>
> Yeah, the GUI is problematic, as the changes are very substantial, and will
> need lots of testing. I just now tried to build and run on OS/X and got
>
> shp2pgsql-gui(77973) malloc: *** error for object 0x100e0e960: pointer being
> freed was not allocated
> *** set a breakpoint in malloc_error_break to debug
>
> Not sure if folks have done a build and test on Win32 yet. For 1.5.2 it
> would be nicer to keep the current GUI, no?
>
> P.
>
> (Of course, I have a reason to not want to change things, having just
> finished a couple workshops full of screenshots of the *old* GUI.)
>
> On Mon, Aug 2, 2010 at 3:45 AM, Mark Cave-Ayland
> <mark.cave-ayland at siriusit.co.uk> wrote:
>> Paul Ramsey wrote:
>>
>>> I am fine with a release. Let me know when you feel the branch has
>>> risen to the level of cutting a tar ball, or do you think we are there
> right now?
>>>
>>> P.
>>
>> The changelog looks reasonably sensible, although I didn't realise
>> until just now that Mark's shp2pgsql GUI changes had been merged into 1.5
> branch.
>> IMO that's quite a large change for a bugfix release on an existing
> branch.
>>
>> The other issue, of course, is that yesterday there was an API change
>> in the 9.0 analyze function:
>> http://archives.postgresql.org/pgsql-committers/2010-08/msg00013.php.
>> We should code up a fix for this before cutting the release.
>>
>>
>> ATB,
>>
>> Mark.
>>
>> --
>> Mark Cave-Ayland - Senior Technical Architect PostgreSQL - PostGIS
>> Sirius Corporation plc - control through freedom
>> http://www.siriusit.co.uk
>> t: +44 870 608 0063
>>
>> Sirius Labs: http://www.siriusit.co.uk/labs
>> _______________________________________________
>> postgis-devel mailing list
>> postgis-devel at postgis.refractions.net
>> http://postgis.refractions.net/mailman/listinfo/postgis-devel
>>
> _______________________________________________
> postgis-devel mailing list
> postgis-devel at postgis.refractions.net
> http://postgis.refractions.net/mailman/listinfo/postgis-devel
>
>
> _______________________________________________
> postgis-devel mailing list
> postgis-devel at postgis.refractions.net
> http://postgis.refractions.net/mailman/listinfo/postgis-devel
>