Testing

[Paul Ramsey-4]

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@...
http://postgis.refractions.net/mailman/listinfo/postgis-devel

[Kevin Neufeld]

Paul Ramsey wrote:
> 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.
>

I agree.  Looking at the Hudson, the automatic build environment I've been using to test/build the docs and packages,
they roll out a new micro release after a mere handful of bugs have been fixed (which is why the current micro is 332).

-- Kevin
_______________________________________________
postgis-devel mailing list
postgis-devel@...
http://postgis.refractions.net/mailman/listinfo/postgis-devel

[Paragon Corporation-2]

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@...
[mailto:postgis-devel-bounces@...] 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@...
http://postgis.refractions.net/mailman/listinfo/postgis-devel



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

[Mark Cave-Ayland-3]

Paul Ramsey wrote:

> 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

Nice comment lol ;)  Incidentally I'll be back on the bug-fixing warpath
this week, so even more things are likely to get bashed around even more...

I have absolutely no problem with Paul fixing bugs and closing tickets
as he feels, however in a few ticket threads, several different
solutions have been proposed and it's not clear which one of these has
been chosen when the final close-off message simply reads "Fixed at
rXXXX". I think in these cases a more verbose comment explaining which
solution has been implemented would be appropriate.


ATB,

Mark.

--
Mark Cave-Ayland - Senior Technical Architect
PostgreSQL - PostGIS
Sirius Corporation plc - control through freedom
http://www.siriusit.co.uk
t: [phone]

Sirius Labs: http://www.siriusit.co.uk/labs
_______________________________________________
postgis-devel mailing list
postgis-devel@...
http://postgis.refractions.net/mailman/listinfo/postgis-devel