You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mahout.apache.org by Grant Ingersoll <gs...@apache.org> on 2009/09/12 20:45:08 UTC
0.2 planning
Here's the list of unresolved issues for 0.2:
https://issues.apache.org/jira/secure/BrowseVersion.jspa?id=12310751&versionId=12313278&showOpenIssuesOnly=true
Can we start to work towards whittling these down and getting 0.2
out? Maybe by mid-October?
-Grant
Re: 0.2 planning
Posted by David Hall <dl...@cs.berkeley.edu>.
Any reason we haven't closed LDA yet
https://issues.apache.org/jira/browse/MAHOUT-123 ?
-- David
On Sat, Sep 12, 2009 at 11:45 AM, Grant Ingersoll <gs...@apache.org> wrote:
> Here's the list of unresolved issues for 0.2:
> https://issues.apache.org/jira/secure/BrowseVersion.jspa?id=12310751&versionId=12313278&showOpenIssuesOnly=true
>
> Can we start to work towards whittling these down and getting 0.2 out?
> Maybe by mid-October?
>
> -Grant
>
Re: 0.2 planning
Posted by Grant Ingersoll <gs...@apache.org>.
By all means, everyone, feel free to mark things as 0.2 or not. And,
also feel free to assign yourself and work on them and commit.
On Sep 12, 2009, at 3:26 PM, Robin Anil wrote:
> +1 for refactor and another release soon after
> i think MAHOUT-157 FPGrowth needs more work in terms of optimisation
> and
> test cases. It may or may not be ready for the mid-oct release. It
> could be
> pushed on to the next release if its done soon after 0.2. I can
> therefore
> focus more on CBayes/Bayes documentation, examples. conversion to
> writable
> among other things for 0.2
>
> Robin
Re: 0.2 planning
Posted by Robin Anil <ro...@gmail.com>.
+1 for refactor and another release soon after
i think MAHOUT-157 FPGrowth needs more work in terms of optimisation and
test cases. It may or may not be ready for the mid-oct release. It could be
pushed on to the next release if its done soon after 0.2. I can therefore
focus more on CBayes/Bayes documentation, examples. conversion to writable
among other things for 0.2
Robin
Re: 0.2 planning
Posted by Sean Owen <sr...@gmail.com>.
I am ready for 0.2 myself. I do not have any changes/fixes in mind
that I think must be in 0.2 -- have made enough changes for one point
release myself.
I would like to continue with some movement of code in the common
packages, changing code to reuse common code more. I will create
issues for this but do not view it as a blocker for 0.2 at all.
Yes let us keep up the momentum with another release soon. From 'my'
part of the code, the improvements are significant, and want to get
them in the field ASAP.
Sean
On Sat, Sep 12, 2009 at 7:45 PM, Grant Ingersoll <gs...@apache.org> wrote:
> Here's the list of unresolved issues for 0.2:
> https://issues.apache.org/jira/secure/BrowseVersion.jspa?id=12310751&versionId=12313278&showOpenIssuesOnly=true
>
> Can we start to work towards whittling these down and getting 0.2 out?
> Maybe by mid-October?
>
> -Grant
>
Re: 0.2 planning
Posted by Jeff Eastman <jd...@windwardsolutions.com>.
I propose leaving MAHOUT-167 out of 0.2 for the reasons which Sean
mentioned previously. MAHOUT-136 is, afaict, done and can probably be
closed. Grant, you had some comments in the issue; have they been resolved?
Grant Ingersoll wrote:
> Here's the list of unresolved issues for 0.2:
> https://issues.apache.org/jira/secure/BrowseVersion.jspa?id=12310751&versionId=12313278&showOpenIssuesOnly=true
>
>
> Can we start to work towards whittling these down and getting 0.2
> out? Maybe by mid-October?
>
> -Grant
>
>