mahout-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Owen (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (MAHOUT-425) Should the release directory have changed when Apache Mahout was promoted to a top level project?
Date Sat, 31 Jul 2010 14:42:16 GMT

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

Sean Owen resolved MAHOUT-425.
------------------------------

         Assignee: Sean Owen
    Fix Version/s: 0.3
       Resolution: Fixed

I copied the files within /www/www.apache.org/dist and AFAIK it will eventually mirror

> Should the release directory have changed when Apache Mahout was promoted to a top level
project?
> -------------------------------------------------------------------------------------------------
>
>                 Key: MAHOUT-425
>                 URL: https://issues.apache.org/jira/browse/MAHOUT-425
>             Project: Mahout
>          Issue Type: Question
>         Environment: All
>            Reporter: Peter Goldstein
>            Assignee: Sean Owen
>            Priority: Minor
>             Fix For: 0.3
>
>
> I noticed that the Apache Mahout releases are still found at this link - http://www.apache.org/dyn/closer.cgi/lucene/mahout/
- which is a subdirectory of the Lucene release directory.
> When I look at the top level Mahout release link - http://www.apache.org/dyn/closer.cgi/mahout/
- all I see is an empty directory.  Shouldn't historical releases be copied to this directory,
and subsequent builds be created here?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message