[postgis-devel] Testing

[Paragon Corporation]

Paul,

I'm not so concerned about that as weighing the benefit of the change (some
we had slated for 2.0) like the RFC...
verses the chance that its going to cause disastrous effects and the speed
at which you are fixing things.

Most bugs are discovered in production after all.  Even during beta
releases, people don't take things quite as seriously until you mark it as
production.  And if you mark something as production that isn't well --
people will trust you much less.

The probability of breaking something is high if you start throwing things
in rapidly, as you can't easily determine which change broke what.  Sorry I
guess my conservative engineering background is seeping thru :).

So perhaps I'm a bit too cautious and you are a bit too loose, and somewhere
in between is a nice middle ground.

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: Friday, November 06, 2009 5:19 PM
To: PostGIS Development Discussion
Subject: [postgis-devel] Testing

In a ticket (!!!!) <http://trac.osgeo.org/postgis/ticket/230> Regina
comments,

"I'm also very concerned about the rate you are closing things off :).
I should be excited, but all I can think is "Paul, stay away from the
caffeine". When are we going to have time to test all this."

You're an amazing tester, Regina, but there's only the one of you. If you
have to choose between testing and rolling beta releases this month, roll
the releases. Getting alpha and beta releases out will identify the issues
that we need to fix before going to final.

Paul
_______________________________________________
postgis-devel mailing list
postgis-devel at postgis.refractions.net
http://postgis.refractions.net/mailman/listinfo/postgis-devel