Received: from magus.postgresql.org (magus.postgresql.org [87.238.57.229])
	by mail.postgresql.org (Postfix) with ESMTP id 1E39CC83CB2
	for <pgsql-www@postgresql.org>; Tue, 10 Jul 2012 15:37:35 -0300 (ADT)
Received: from cronos.madness.at ([2a02:16a8:dc41::10])
	by magus.postgresql.org with esmtp (Exim 4.72)
	(envelope-from <stefan@kaltenbrunner.cc>) id 1SofJU-00021K-TB
	for pgsql-www@postgresql.org; Tue, 10 Jul 2012 18:37:34 +0000
Received: from mastermind.kaltenbrunner.cc ([2001:470:7a2d::22])
	by cronos.madness.at with esmtpsa (TLS1.0:RSA_AES_256_CBC_SHA1:32)
	(Exim 4.72) (envelope-from <stefan@kaltenbrunner.cc>)
	id 1SofJ4-00063c-LG; Tue, 10 Jul 2012 20:37:12 +0200
Message-ID: <4FFC764B.4060800@kaltenbrunner.cc>
Date: Tue, 10 Jul 2012 20:36:59 +0200
From: Stefan Kaltenbrunner <stefan@kaltenbrunner.cc>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US;
	rv:1.9.2.24) Gecko/20111120 Icedove/3.1.16
MIME-Version: 1.0
To: Bruce Momjian <bruce@momjian.us>
CC: Josh Berkus <josh@agliodbs.com>,
	Alvaro Herrera <alvherre@commandprompt.com>,
	Peter Geoghegan <peter@2ndquadrant.com>, Tom Lane <tgl@sss.pgh.pa.us>,
	Magnus Hagander <magnus@hagander.net>, w^3 <pgsql-www@postgresql.org>
Subject: Re: 9.2beta web issues
References: 
 <CABUevEybVA7dEeBUekoinBpLn40jWjhYHdhzPJj=f-p1ZYPRgg@mail.gmail.com>
	<1341525030-sup-6100@alvh.no-ip.org>
	<2405.1341528250@sss.pgh.pa.us> <4FF72D24.1010206@kaltenbrunner.cc>
	<CAEYLb_Uycpj6h1f5_1dXquk1c2XOVeSYDaPtKHHWibQbOpXD8w@mail.gmail.com>
	<4FFB67BD.90908@agliodbs.com> <4FFC6AA0.1060903@kaltenbrunner.cc>
	<4FFC6C8E.2060305@agliodbs.com>
	<1341943550-sup-2118@alvh.no-ip.org>
	<4FFC7124.3050700@agliodbs.com> <20120710182957.GB31912@momjian.us>
In-Reply-To: <20120710182957.GB31912@momjian.us>
X-Enigmail-Version: 1.1.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Pg-Spam-Score: -1.9 (-)
X-Archive-Number: 201207/83
X-Sequence-Number: 20832

On 07/10/2012 08:29 PM, Bruce Momjian wrote:
> On Tue, Jul 10, 2012 at 11:15:00AM -0700, Josh Berkus wrote:
>> BTW, I'm mainly interested in preserving the pgsql-testers mailing list
>> for future use; I'm still hoping to find time to get a serious volunteer
>> QA effort together, in which case it will need a mailing list.  So we
>> could kill off pgsql-testers now, but I'll probably just be asking to
>> revive it next year if you do.
> 
> I have never been a fan of our cycle of "let's try something --- oh,
> that didn't work --- let's not tell anyone --- (years later) why is this
> here".  I vote we remove it, and in the future, if we decide not to use
> something, let's not assume some amazing idea is going to fix it ---
> let's just remove it proactively.

I fully agree - if we ever figure out how that "serious QA" thingy is
going to work we can easily add a dedicated and maybe even more
appropriately named list. refacturing a list that we have people
subscribed to under a specific purpose into something that might be
something entirely different "next year" seems completely wrong anyway...


Stefan