| From: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
|---|---|
| To: | Dann Corbit <DCorbit(at)connx(dot)com> |
| Cc: | Jason Earl <jason(dot)earl(at)simplot(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Two weeks to feature freeze |
| Date: | 2003-06-21 05:13:32 |
| Message-ID: | 20030621131237.D14306-100000@houston.familyhealth.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> We (at CONNX Solutions Inc.) have a formal release procedure that
> includes many tens of thousands of automated tests using dozens of
> different platforms. There are literally dozens of machines (I would
> guess 70 or so total) running around the clock for 7 days before we even
> know if we have a release candidate. The QA team is distinct from the
> development team, and if they say "FLOP!" the release goes nowhere. No
> formal release until QA passes it.
PostgreSQL has a comprehensive regression suite that is run by the
developers all the time...
> If there is no procedure for PostgreSQL of this nature, then there
> really needs to be. I am sure that MySQL must have something in place
> like that. Their "Crash-Me" test suite shows (at least) that they have
> put a large effort into testing.
No, it means they've put a crap effort into trying to make other databases
look bad...
Chris
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dann Corbit | 2003-06-21 05:19:12 | Re: Two weeks to feature freeze |
| Previous Message | Christopher Kings-Lynne | 2003-06-21 05:10:36 | Re: Commands to change name, schema, owner |