You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Henk Penning (JIRA)" <ji...@apache.org> on 2013/08/14 16:42:49 UTC

[jira] [Commented] (INFRA-6654) AOO 4.1 dist options

    [ https://issues.apache.org/jira/browse/INFRA-6654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13739729#comment-13739729 ] 

Henk Penning commented on INFRA-6654:
-------------------------------------

I think we should stick to the policy of having max 1 "binaries" release on the mirrors.
Quite a few mirrors indicated that they can easily run out of disk-space.
Note that the "far away" mirrors (far from om .eu and .us) are often those with the fewest resources.
Having binaries is more inportant for "far away" mirrors than "close" mirrors.
I object to policies that push poor, "far away" mirrors to an opt-out.

Since it takes about a week to get a binaries release on the mirrors, a new release implies that
mirrors are without a release for about a week. I think it's best to schedule that week just before
the release date of the new release.

So, as long as the size of a release doesn't decrease a lot (say 50%), the best plan would be :
- one week before the release date, remove the binaries from the mirrors ;
- use that week to get the new binaries on the mirrors.
                
> AOO 4.1 dist options
> --------------------
>
>                 Key: INFRA-6654
>                 URL: https://issues.apache.org/jira/browse/INFRA-6654
>             Project: Infrastructure
>          Issue Type: Bug
>            Reporter: #asfinfra IRC Bot
>
> Review how we plan to distribute AOO, whether any changes are required by SF / ASF / AOO to make the process more efficient in resources / admin overhead / etc.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira