> 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...


---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?


Reply via email to