[postgis-devel] 1.4.1rc1

[Mark Cave-Ayland]

Paul Ramsey wrote:

>> I'd still like independent confirmation from someone first that I haven't
>> broken anything in shp2pgsql/pgsql2shp with the last set of patches. Plus I
>> think we really ought to get #316 rolled in at the same time - I don't see
>> that we are super desperate to get out a 1.4.1 in the next day or so.
> 
> That kind of logic will never lead to a release... :/ I agree, #316 as
> a crasher should go first.
> 
> P.

No, I don't think that is the case at all. We are due a new 1.4 branch 
release, but I don't see anything in there that is critical enough to 
make a difference as to whether we release this week or beginning of 
next week.

The issue is sadly that pushing out a release has non-zero cost to 
packagers, and Regina will back me up on this. I know that I used to 
spend anywhere between 8 - 24 hours building and regression testing the 
3 different installers just on Win32 (and this takes much longer if any 
of the regression tests fail). Hence if we push out a release with known 
issues that require fixing within 1-2 weeks, then the packagers will 
struggle to keep up.


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