On 3 September 2013 08:05, Andrea Pescetti <pesce...@apache.org> wrote:
> On 03/09/2013 sebb wrote:
>>
>> Are you suggesting pointing users to the archives for current sigs and
>> hashes?
>> If so, I don't think that's a good idea.
>
>
> Maybe it isn't, but using dist is worse:
> - Everything that lives on dist is temporary
> - You end up with tons on liks to update (and some cannot really be fixed,
> such as URLs in PDFs obtained from security announcements, or URLs
> copy-pasted from them into blog posts)

That is unlikely to apply to sigs and hashes.

> - The bandwidth required for downloading hashes is obviously very tiny

But the user population is huge compared with other ASF products.

> So I really prefer to use permanent URLs (from archive) for hashes.

AFAIK all other ASF products link to the ASF mirrors for current releases.

>
>> Updating the links to point to the archive server should be done for
>> both artifacts and sigs/hashes at the same time.
>
>
> Artifacts in our case are much more manageable since we have one link in
> other.html ; in that case, it's clearly best to use the dist link until the
> version is available and the archive link when it is no longer available on
> dist.

I don't follow how the sigs/hashes are any different from the
downloads they protect.
Either they are current, and on the ASF mirrors, or they have been
superseded and are on the archive host.

>
> Regards,
>   Andrea.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Reply via email to