www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Henk Penning (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-8756) Should dist/zzz be in SVN?
Date Thu, 04 Dec 2014 10:52:12 GMT

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

Henk Penning commented on INFRA-8756:

> I had assumed these would depend on whether the host served all releases or 
> most (excluding AOO). 

The mirrors pick up either module "apache-dist" or "apache-dist-most" ;
In module "apache-dist", file "zzz/rsync-module/apache-dist-most" is
excluded ; and vice versa for module "apache-dist-most".

There is no "the SVN dist tree" ; there are two ; and they differ re: timestamps.
I propose to maintain a WC of dist on mino and use that to feed the rsync servers.

If we can track the changes in dist on mino, we can have (almost) instantaneous
updates on our rsync servers.


> Should dist/zzz be in SVN?
> --------------------------
>                 Key: INFRA-8756
>                 URL: https://issues.apache.org/jira/browse/INFRA-8756
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: Mirrors, Website
>            Reporter: Sebb
> The folder dist/zzz is used for mirroring.
> Some files are test files, and some are work files.
> The preset files are unlikely to change, but at present I think they are not in SVN anywhere.

> Probably should add the "fixed" files to SVN and add zzz to svnpubsub.
> ===
> Once that has been done, perhaps consider using svnpubsub to update the whole of dist
as a single unit. That would simplify the scripts (which were presumably introduced to cater
for the original mixed mode publishing?). There would be no need to add new TLPs to the list
- it would happen automatically when another folder is added to dist/release. Would that have
any disadvantages?

This message was sent by Atlassian JIRA

View raw message