[jira] Commented: (MAHOUT-69) 0.1 RELEASE TODO

["Grant Ingersoll (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MAHOUT-69?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12640238#action_12640238 ] 

Grant Ingersoll commented on MAHOUT-69:
---------------------------------------

>From Hoss's email: http://mahout.markmail.org/message/n3x3mcdhprqqvexe?q=0%2E1

FWIW, looking at this RC...

chrish@asimov:~/tmp/mahout$ md5sum apache-mahout-0.1.tgz
71325edfef9b3f591973e7e7a13d0385  apache-mahout-0.1.tgz

...i don't have JAva 6 installed so i couldn't test re-compilation or 
running any of the examples, but i do have some ocmments on the contents 
of the release...

1) is the included README intended to have "TODO" as the entire 
"Getting Started" section ?

2) the javadocs list the version as: 0.1.2008.09.29.20.57.15 ... looks 
like the specversion property wasn't set when they were generated.

3) core/build.xml has javadoc.years set to "2006 - ${year}" ... none of 
this code is as old as 2006, correct? so i don't think that's legitimate 
to claim.

4) lib/ contains junit-3.8.2.jar but junit is not mentioned in NOTICE.txt 
... I'm also pretty sure the JUnit license is suppose to be included in 
LICENSE.txt (not lib/junit-LICENSE.html)

5) ditto #4 for everything in core/lib and example/lib that isn't already 
included in NOTICE.txt and/or LICENSE.txt as appropriate (i don't know 
what most of those jars are, maybe they are mostly accounted for, but at a 
minimum I don't see easymock mentioned)

6) the only javadocs i see pre-built are in docs/api/ and they seem to 
corrispond with core/src/main/ .. should there be pre-built javadocs for 
examples/src/main/ as well?

7) it seems really bad that there is *zero* documentation provided beyond 
the javadocs ... particularly considering the javadocs have no top level 
info (ie: there is no overview.html in core/src/main/java/)

There isn't even a single link to mahout homepage or wiki *anywhere* in 
the release...

chrish@asimov:~/tmp/mahout/apache-mahout-0.1$ grep -r "lucene.apache.org/mahout" .
chrish@asimov:~/tmp/mahout/apache-mahout-0.1$ grep -r "cwiki.apache.org" .
chrish@asimov:~/tmp/mahout/apache-mahout-0.1$          


> 0.1 RELEASE TODO
> ----------------
>
>                 Key: MAHOUT-69
>                 URL: https://issues.apache.org/jira/browse/MAHOUT-69
>             Project: Mahout
>          Issue Type: Task
>    Affects Versions: 0.1
>            Reporter: Grant Ingersoll
>             Fix For: 0.1
>
>
> We need to figure out all the things that need to be done for a 0.1 release.
> These include, but are not limited to:
> - Legal issues (NOTICES.txt, license files, etc.)
> - Documentation
> - Wiki page on making releases (See Lucene or Solr wiki page on said topic)
> - Release Managers should setup signatures
> - Remaining issues to be resolved for 0.1.  We should go through the issues and make decisions by setting the fix version to be 0.1
> Others?  I've personally never done an Apache release before, so we will want to take our time and make sure things are right.

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