Please lets leave that sort of issue to infrastructure to worry about- what we do about mirrors that cannot support the AOO bandwidth needs is not a concern for AOO itself.
>________________________________ > From: Pedro Giffuni <[email protected]> >To: [email protected]; Joe Schaefer <[email protected]> >Sent: Wednesday, March 21, 2012 12:31 PM >Subject: Re: Sourceforge and AOO 3.4 distribution > > >--- Mer 21/3/12, Joe Schaefer ha scritto: >... >> Right now the ASF has roughly 250 >> mirrors, >> of which atm I'd expect 50 or so to drop us if >> we start carrying AOO releases. That means >> we'd have about twice as many mirrors as >> the mirrorbrain OOo service has, so we should >> be in better shape overall than what happened >> in the past, assuming we do something smart >> about staggering the Update service. There >> will be no way to surprise anybody about the >> release timing for an AOO release as at least >> a week of public discussion/voting will precede it. >> >> > >FWIW, I am pretty sure the problem will be >windows binaries: if we did a source-only >release we probably wouldn't lose any mirrors. > >Perhaps there is some way to make the binary >packages opt-out for the mirrors? > >Pedro. > >> >> I still would like to strongly suggest that >> someone on the PPMC step up NOW and offer to contact >> existing mirror operators to get them to cover >> some of our losses. >> > > > >
