Coverity Inspected, 20 bugs detected!

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: pgsql-www(at)postgresql(dot)org
Cc: pgsql-advocacy(at)postgresql(dot)org
Subject: Coverity Inspected, 20 bugs detected!
Date: 2005-07-23 22:24:54
Message-ID: 200507231524.54443.josh@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-advocacy pgsql-www

Folks,

Sorry to dual-list this, but there's dual aspects to it.

EnterpriseDB, Neil Conway and (earlier) Sean Chittenden worked with
Coverity to do static code analysis of PostgreSQL. We came up very clean
(20 bugs in our 3/4 million lines of code) but part of that was due to
previous work. As such, we're now entitled to put a "Coverity Inspected"
web sticker up on our site somewhere.

So, two questions:

1) Do we want to put up a Coverity Inspected button? On the plus side,
Oracle, MySQL and BerkeleyDB (as well as FreeBSD) have all gone through
the Coverity checker, so it says good things about our competitiveness to
other database products. On the negative side, do we really care?

2) If we want to put up the button, *where*? We don't really have a page
on the web site for "certifications and awards", but maybe we ought to?

--
--Josh

Josh Berkus
Aglio Database Solutions
San Francisco

Responses

Browse pgsql-advocacy by date

  From Date Subject
Next Message Marc G. Fournier 2005-07-23 23:10:52 Re: Coverity Inspected, 20 bugs detected!
Previous Message Jeff Davis 2005-07-23 21:28:01 Re: [HACKERS] Enticing interns to PostgreSQL

Browse pgsql-www by date

  From Date Subject
Next Message Marc G. Fournier 2005-07-23 23:10:52 Re: Coverity Inspected, 20 bugs detected!
Previous Message Marc G. Fournier 2005-07-20 23:53:41 Re: nightly snapshots broken since mid-June