Received: from localhost (maia-5.hub.org [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id 078039FA502 for ; Mon, 5 Feb 2007 15:52:37 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-new, port 10024) with ESMTP id 34879-01 for ; Mon, 5 Feb 2007 15:52:29 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from svr2.hagander.net (svr2.hagander.net [88.198.128.226]) by postgresql.org (Postfix) with ESMTP id 7A1B99FA354 for ; Mon, 5 Feb 2007 15:52:31 -0400 (AST) Received: from [192.168.199.197] (c213-100-160-41.swipnet.se [213.100.160.41]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by svr2.hagander.net (Postfix) with ESMTP id 6D9D3DCC390; Mon, 5 Feb 2007 20:52:30 +0100 (CET) Message-ID: <45C78B00.4020203@hagander.net> Date: Mon, 05 Feb 2007 20:52:32 +0100 From: Magnus Hagander User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 To: Josh Berkus CC: pgsql-www@postgresql.org Subject: Re: How to coordinate web team for security releases? References: <200702051128.13819.josh@agliodbs.com> In-Reply-To: <200702051128.13819.josh@agliodbs.com> X-Enigmail-Version: 0.94.2.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200702/27 X-Sequence-Number: 11432 Josh Berkus wrote: > WWW core team, > > I need a way to coordinate with you around preparing postgresql.org for > upcoming releases, especially for security releases where it's critical that > the timing be tight. Due to some issues with this last release, pgsql-www > obviously isn't the right venue. > > What I need is a non-public list for this, so that I can ask for web site > changes 3-4 days ahead without it becoming a news item. Will that really help? In this case, the files were uploaded to the ftp site long before you made your post to the -www list... Does it really make a difference? //Magnus