Received: from localhost (maia-4.hub.org [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 917BF9FB1EA for ; Mon, 5 Feb 2007 16:08:24 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-new, port 10024) with ESMTP id 26409-03 for ; Mon, 5 Feb 2007 16:08:17 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from cronos.madness.at (madness.at [217.196.146.217]) by postgresql.org (Postfix) with ESMTP id 5F1249FA50C for ; Mon, 5 Feb 2007 16:08:17 -0400 (AST) Received: from mastermind.kaltenbrunner.cc ([83.215.233.60]) by cronos.madness.at with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.62 (FreeBSD)) (envelope-from ) id 1HEA8E-000Od5-Nz; Mon, 05 Feb 2007 21:08:15 +0100 Message-ID: <45C78EA6.4080008@kaltenbrunner.cc> Date: Mon, 05 Feb 2007 21:08:06 +0100 From: Stefan Kaltenbrunner User-Agent: Icedove 1.5.0.9 (X11/20061220) MIME-Version: 1.0 To: Greg Sabino Mullane CC: pgsql-www@postgresql.org Subject: Re: How to coordinate web team for security releases? References: In-Reply-To: X-Enigmail-Version: 0.94.1.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/30 X-Sequence-Number: 11435 Greg Sabino Mullane wrote: > >> 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. > > I think Dave's idea of -packagers works fine, there should be enough overlap. > > What we also need is a better way to update the mirrors in a timely manner. the fact that new releases are coming up also got announced on IRC over three days ago and we have >300 people there ... Stefan