[postgis-devel] Call for 1.5.2 release

[Mark Cave-Ayland]

Paragon Corporation 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?

Maybe Mark accidentally merged into the wrong branch? Although I think 
Mark has done a great job here, I would like to propose that we revert 
from 1.5 branch and apply to trunk instead.

The aim of point releases is that they should contain bugfixes and not 
new features; we should be able to push out a new bugfix release without 
having to jump through the same testing hoops we do for a full release.

As Paul also points out, managing training materials is going to be a 
nightmare with some 1.5 releases on older versions and some on new 
versions - it would be like a Microsoft security update changing the 
interface on XP to look like Windows 7. As a project, I feel we need to 
be much more disciplined about this.

+1 for reverting from 1.5 branch and re-applying to trunk.


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