infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Lambertus (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (INFRA-16124) Strategy for renamed mailing lists
Date Tue, 24 Apr 2018 06:17:00 GMT

     [ https://issues.apache.org/jira/browse/INFRA-16124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Chris Lambertus updated INFRA-16124:
------------------------------------
    Status: Waiting for user  (was: Waiting for Infra)

Does your recent update for mapping renamed lists adequately resolve this?

> Strategy for renamed mailing lists
> ----------------------------------
>
>                 Key: INFRA-16124
>                 URL: https://issues.apache.org/jira/browse/INFRA-16124
>             Project: Infrastructure
>          Issue Type: Task
>          Components: Mail Archives
>            Reporter: Sebb
>            Priority: Major
>
> Mailing lists are sometimes renamed.
> For example, infrastructure-issues@apache.org is now issues@infra.apache.org.
> On minotaur, where the mboxes are initially stored, the mbox files have been renamed
to agree with the new list name.
> However the mail archives are served from eos (mail-archives.apache.org).
> This has a synched copy of the mboxes from minotaur, and a separate area where the mboxes
are indexed for display by mod_mbox. The files in this area are not only ever updated, so
there are now copies of all the original files in the new area as well. There are mails shown
under 
> http://mail-archives.apache.org/mod_mbox/www-infrastructure-issues/
> up to Oct 2016 (when the list was renamed).
> The mails from Oct 2016 are shown here:
> http://mail-archives.apache.org/mod_mbox/infra-issues/
> Earlier mails from the original list are not currently shown because they have not been
indexed.
> It's difficult to follow the history across the rename.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message