Received: from maia.hub.org (maia-3.hub.org [200.46.204.243]) by mail.postgresql.org (Postfix) with ESMTP id 4B0721337BE9 for ; Tue, 3 May 2011 17:25:23 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.243]) (amavisd-maia, port 10024) with ESMTP id 72663-09 for ; Tue, 3 May 2011 20:25:15 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from smtp-4.01.com (smtp-4.01.com [38.102.63.183]) by mail.postgresql.org (Postfix) with ESMTP id 44FAD1337BE4 for ; Tue, 3 May 2011 17:25:15 -0300 (ADT) Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp-4.01.com (Postfix) with ESMTP id 29B6C3BCE37; Tue, 3 May 2011 15:25:15 -0500 (CDT) Received: from smtp-4.01.com ([127.0.0.1]) by localhost (smtp-4.01.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p89gDb5n6Kca; Tue, 3 May 2011 15:25:15 -0500 (CDT) Received: by smtp-4.01.com (Postfix, from userid 99) id ED88E3BCD1F; Tue, 3 May 2011 15:25:14 -0500 (CDT) Received: from Sidney-Stratton.local (70-36-143-243.dsl.dynamic.sonic.net [70.36.143.243]) by smtp-4.01.com (Postfix) with ESMTPSA id 624C03BCEB4; Tue, 3 May 2011 15:25:14 -0500 (CDT) Message-ID: <4DC064A9.8090509@agliodbs.com> Date: Tue, 03 May 2011 13:25:13 -0700 From: Josh Berkus Organization: PostgreSQL Experts Inc. User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2.15) Gecko/20110303 Lightning/1.0b2 Thunderbird/3.1.9 MIME-Version: 1.0 To: Magnus Hagander CC: Andrew Dunstan , postgres hackers Subject: Re: A small step towards more organized beta testing References: <4DBEF423.2060601@agliodbs.com> <4DC04EB7.5070807@agliodbs.com> <4DC05EBA.2000900@agliodbs.com> <4DC05FAE.9010206@dunslane.net> In-Reply-To: X-Enigmail-Version: 1.1.1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.9 tagged_above=-5 required=5 tests=BAYES_00=-1.9 X-Spam-Level: X-Archive-Number: 201105/90 X-Sequence-Number: 187124 >> Are we really running a Google spreadsheet as in effect a bug tracker? > > And why are we so inistant on not posting bug reports to pgsql-bugs? We're not. However: a) pgsql-bugs doesn't help us to get all of the various test information without a lot of back-and-forth with the submitter (platform, version, install method, test run, etc.) b) pgsql-bugs is for failures only, and not for successful tests, and we need successful tests as well to know how we're doing. However, that does suggest that having the eventual test report app (working on it), post failures to pgsql-bugs on some kind of moderated basis. BTW, if anyone knows of a specific *testing* application out there which handles user testing, then please speak up before I write one. -- Josh Berkus PostgreSQL Experts Inc. http://pgexperts.com