Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id D79902E0064 for ; Tue, 25 Mar 2008 13:48:34 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 64522-05-4 for ; Tue, 25 Mar 2008 13:48:25 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from alexis.jtlnet.com (alexis.jtlnet.com [69.36.9.81]) by postgresql.org (Postfix) with ESMTP id E153F2E0075 for ; Tue, 25 Mar 2008 13:48:12 -0300 (ADT) Received: from [192.168.10.103] (cpe-075-177-177-228.nc.res.rr.com [::ffff:75.177.177.228]) (TLS: TLSv1/SSLv3,256bits,AES256-SHA) by alexis.jtlnet.com with esmtp; Tue, 25 Mar 2008 12:47:37 -0400 id 00080642.47E92CA9.00007AF0 Message-ID: <47E92CBF.1000107@dunslane.net> Date: Tue, 25 Mar 2008 12:47:59 -0400 From: Andrew Dunstan User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.8.0.12) Gecko/20071019 Fedora/1.0.9-3.fc6 pango-text SeaMonkey/1.0.9 MIME-Version: 1.0 To: Tom Lane CC: Andrew Sullivan , pgsql-hackers@postgresql.org Subject: Re: [pgsql-www] New email list for emergency communications References: <47E7F825.9020902@kaltenbrunner.cc> <200803241909.m2OJ9RX08326@momjian.us> <20080324192014.GI5484@alvh.no-ip.org> <47E82D9D.6040000@dunslane.net> <20080325145735.GB28405@crankycanuck.ca> <21700.1206460234@sss.pgh.pa.us> In-Reply-To: <21700.1206460234@sss.pgh.pa.us> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200803/974 X-Sequence-Number: 115775 Tom Lane wrote: > Andrew Sullivan writes: > >> On Mon, Mar 24, 2008 at 06:39:25PM -0400, Andrew Dunstan wrote: >> >>> perusing a mailbox again. We have unfortunately been badly underprepared >>> for this. >>> > > >> Surely that there is an emerging consensus to that effect means that it's >> not as unfortunate as it might be? I seem to recall the original >> announcement suggesting this was an experiment. I wouldn't expect the first >> couple rounds to go without a hitch; as long as there is procedural >> improvement the next time, that's a good thing, right? >> > > Yeah, we expected to have glitches. I think we now have a much better > idea what sort of status-tracking support we need for future fests. > > > Yes. I'm not meaning to whine, sorry if it comes over like that. It looks to me like we need a sort of prep phase for a commit-fest, so the people switching into commit-fest mode when it starts can do so with little friction. cheers andrew