Re: Propagating Releases to Mirrors

[Justin Mason <jm...@jmason.org>]

Michael Parker writes:
> Justin Mason wrote:
> > Apache SpamAssassin 3.2.3 is now available!  This is a maintenance
> > release of the 3.2.x branch.
> > 
> > Downloads are available from:
> >   http://spamassassin.apache.org/downloads.cgi
> > 
> 
> When we are doing releases we really need to let them propagate to the
> mirrors a little (ideally 24hrs) before we announce.  Otherwise folks
> will get Not Found errors right off the bat until places start picking
> them up.
> 
> I know we can add a date string to the download.cgi link but I
> understand that is discouraged because it adds extra load to the server.

Have you got a reference for that?  as far as I know, the date
string is designed expressly to take care of this situation.
(Mind you, my bad for not *using* the date string variant.)

> I think we should wait at least 6-10hrs after pushing the files out
> before announcing.  That gives mirrors time to fetch the packages, give
> CPAN a chance to circulate, etc etc.  A little more baking won't hurt
> things.

in my opinion the release process is onerous enough without adding
a 6-10 delay halfway through.

--j.

Re: Propagating Releases to Mirrors

[Michael Parker <pa...@pobox.com>]

Justin Mason wrote:
> Michael Parker writes:
>> Justin Mason wrote:
>>> Apache SpamAssassin 3.2.3 is now available!  This is a maintenance
>>> release of the 3.2.x branch.
>>>
>>> Downloads are available from:
>>>   http://spamassassin.apache.org/downloads.cgi
>>>
>> When we are doing releases we really need to let them propagate to the
>> mirrors a little (ideally 24hrs) before we announce.  Otherwise folks
>> will get Not Found errors right off the bat until places start picking
>> them up.
>>
>> I know we can add a date string to the download.cgi link but I
>> understand that is discouraged because it adds extra load to the server.
> 
> Have you got a reference for that?  as far as I know, the date
> string is designed expressly to take care of this situation.
> (Mind you, my bad for not *using* the date string variant.)

Something mentioned on the infrastructure list a little while back but I
can't find an archive to point you at for a reference.


> 
>> I think we should wait at least 6-10hrs after pushing the files out
>> before announcing.  That gives mirrors time to fetch the packages, give
>> CPAN a chance to circulate, etc etc.  A little more baking won't hurt
>> things.
> 
> in my opinion the release process is onerous enough without adding
> a 6-10 delay halfway through.


I don't think it is that unreasonable to add a small delay between the
time the release is uploaded and an email is sent to the lists.  It
would save a bunch of people trying to fetch the release right away but
not being able to find it, or a mirror taking the brunt of the SA
downloads because someone posts a direct link of an up-to-date mirror to
the mailing list.

Michael


> 
> --j.
>