You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mahout.apache.org by "Sean Owen (JIRA)" <ji...@apache.org> on 2010/07/31 16:42:16 UTC
[jira] Resolved: (MAHOUT-425) Should the release directory have
changed when Apache Mahout was promoted to a top level project?
[ 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.