From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Justin Clift <aa2(at)bigpond(dot)net(dot)au> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: beta5 ... |
Date: | 2001-02-20 15:50:57 |
Message-ID: | 12614.982684257@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
>> As a matter of curiosity, is each beta compiled and then regression
>> tested against *every* one of the known "supported" platforms before
>> release?
Who are you expecting to do that, exactly?
One of the differences between Postgres and a proprietary commercial
database is that there is no vast support machinery behind the scenes.
What you see going on on this list is what you get: beta testing
consists of the activities performed and reported by list members.
Normally, if we are about to push out a beta then two or three people
will double-check that the current CVS tip builds and passes regression
on their personal machines. But the "supported platforms" coverage
depicted in the docs consists of all the platforms that are reported to
us as working during the entire beta test period, including many that
the key developers have no direct access to. There's no way that we
could reverse the process and cause that to happen before a beta release
instead of after; certainly no way that we could cause all that effort
to be repeated for each beta version.
If you are using a beta version then you are part of that testing
process, not a beneficiary of something that's happened behind closed
doors.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2001-02-20 16:00:09 | Re: Turkish locale bug |
Previous Message | Peter Eisentraut | 2001-02-20 15:47:04 | Re: enable-debug considered pointless |