public inbox for [email protected]  

help / color / mirror / Atom feed

From: Dave Page <[email protected]>
To: Greg Sabino Mullane <[email protected]>
Cc: [email protected]
Subject: Re: How to coordinate web team for security releases?
Date: Mon, 05 Feb 2007 21:12:58 +0000
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>

Greg Sabino Mullane wrote:
> 
> Dave Page wrote:
>>> 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.
> 
> Well, I was thinking more in terms of something in addition to the daily update,
> such as an hourly (or less) check that would pull in any high-priority changes[1].
> Seems that most of the time-sensitive changes we've needed affect a very small
> subset of the pages and should not be a traffic concern. The good thing about
> such a system is that we would not even need 100% buy-in right away - the ones
> not implementing it would still get the daily update. Eventually we'd want to
> strongly encourage everyone to use it, of course.

A nice idea, but a good number of our mirrors are big mirrors sites who
likely won't want to muck around with special configs for each site they
mirror.

Perhaps we could group the mirrors into 'preferred' and 'normal'
sections, where the preferred ones are all on a 2 or 4 hour update.

Regards, Dave.

view thread (50+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected]
  Subject: Re: How to coordinate web team for security releases?
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox