Message-ID: <45C791C3.8080503@kaltenbrunner.cc>
Date: Mon, 05 Feb 2007 21:21:23 +0100
From: Stefan Kaltenbrunner <stefan@kaltenbrunner.cc>
User-Agent: Icedove 1.5.0.9 (X11/20061220)
MIME-Version: 1.0
To: Dave Page <dpage@postgresql.org>
CC: Greg Sabino Mullane <greg@turnstep.com>,  pgsql-www@postgresql.org
Subject: Re: How to coordinate web team for security releases?
References: <aaa2d19c20d5e3972407cdca46fba834@biglumber.com>
	<45C78F8E.60208@postgresql.org>
In-Reply-To: <45C78F8E.60208@postgresql.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Dave Page wrote:
> 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.

how much traffic are the mirrors handling on average btw ? maybe we do
not actually need 70+ or so offical mirrors and reducing that number
significantly to the ones that can get updated more often might help a bit.


Stefan