Received: from localhost (maia-1.hub.org [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id 6D78D9FB1EA for ; Mon, 5 Feb 2007 16:12:08 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-new, port 10024) with ESMTP id 01389-05 for ; Mon, 5 Feb 2007 16:12:00 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from developer.pgadmin.org (developer.pgadmin.org [63.246.23.140]) by postgresql.org (Postfix) with ESMTP id E1F519FA50C for ; Mon, 5 Feb 2007 16:12:00 -0400 (AST) Received: from [172.16.0.68] ([84.13.224.116]) (authenticated bits=0) by developer.pgadmin.org (8.13.8/8.13.8) with ESMTP id l15JmnHZ015475 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 5 Feb 2007 19:48:50 GMT Message-ID: <45C78F8E.60208@postgresql.org> Date: Mon, 05 Feb 2007 20:11:58 +0000 From: Dave Page User-Agent: Thunderbird 1.5.0.9 (Macintosh/20061207) 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.2 OpenPGP: url=http://www.pgadmin.org/pgp/davepage.pgp Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200702/32 X-Sequence-Number: 11437 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. I don't see how we can do that unless we persuade all the mirrors to update more than once per day, which I doubt the larger ones will do. I guess we could consider reducing the max age of a mirror when we generate the selection pages - but that will mean mirrors will be enabled and disabled at different parts of the day for a few hours at a time. /D