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-9063) dist: drop retired project folders & move .htaccess redirects to parent
Date Sun, 25 Jan 2015 11:47:35 GMT

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

Henk Penning commented on INFRA-9063:

In the currrent setup, it is easy to find the list of retired TLPs: 

grep -l attic.apache.org /dist/*/.htaccess | perl -F/ -ane 'print $F[$#F-1], "\n";'

Take beehive ; I prefer to have stuff regarding "beehive" to be local in "dist/beehive" ;
not somewhere else like "dist/.htaccess", where I-don't-want-to-know-who can mess with it.

If/when the "retire TLP" process is ever automated, it is much easier to fix stuff (only)
in "dist/TLP/" than to (also) fix stuff in "dist/.htaccess".

To make info (in the filesystem) about a retired TLP complete, we could add an optional "date"
 comment to the ".htaccess" file like

# retire-date : yyyy-mm-dd
RedirectMatch permanent .* http://attic.apache.org/projects/<TLP>.html

Do we have permission to fix that for dist/TLP/.htaccess files for

> dist: drop retired project folders & move .htaccess redirects to parent
> -----------------------------------------------------------------------
>                 Key: INFRA-9063
>                 URL: https://issues.apache.org/jira/browse/INFRA-9063
>             Project: Infrastructure
>          Issue Type: Improvement
>          Components: Dists, Mirrors
>            Reporter: Sebb
> At present, retired projects retain their directory under 
> https://dist.apache.org/repos/dist/release/
> However the only content is the .htaccess file which redirects to the Attic.
> As the number of retired projects is bound to increase over time, the dist/release directory
will gradually contain more and more of them.
> Would it not be better to add the redirect to the parent .htaccess file and drop the
directory with its sole file? Is there any need to keep the directory?

This message was sent by Atlassian JIRA

View raw message