Re: How to coordinate web team for security releases?

-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160


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.

[1] Indication of a need to pull in changes could be as simple as an atomic
number stored in a text file somewhere, or by a list of files and timeststamps,
or something else simple yet low traffic.

- --
Greg Sabino Mullane greg@turnstep.com
PGP Key: 0x14964AC8 200702051602
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-----BEGIN PGP SIGNATURE-----

iD8DBQFFx5ufvJuQZxSWSsgRA4SbAKCDm3AGz4+HNHxLGX/mViiLJ93XywCgxiSA
U9pGW39bEZpfOZwVr4EQe0M=
=G7T+
-----END PGP SIGNATURE-----