2010/2/8 Sean :
As for MAHOUT-228 (SGD for logistic regression), I could not continue
the work I started on this during the last two week and don't have
time this week either. Furthermore, we need to align it to a common
api for document vectorizers (factorize out the murmurhash +
randomvectorizer
I suppose yeah :) but I was just being snarky and not serious.
On Mon, Feb 8, 2010 at 3:04 PM, Robin Anil wrote:
> 0.2.5 you mean? otherwise we are skipping numbers :)
On Mon, Feb 8, 2010 at 8:32 PM, Sean wrote:
> On Sun, Feb 7, 2010 at 10:56 PM, Jake Mannix
> wrote:
> > MAHOUT-185 Add mahout shell script for easy
> > launching of various algorithms
>
> This one I'd disagree with, it's not a blocker in any sense, has been
> on the books a while and there's no
On Sun, Feb 7, 2010 at 10:56 PM, Jake Mannix wrote:
> MAHOUT-185 Add mahout shell script for easy
> launching of various algorithms
This one I'd disagree with, it's not a blocker in any sense, has been
on the books a while and there's not evidence of progress. Marking it
for 0.4 in no way means
On Sun, Feb 7, 2010 at 2:46 PM, Sean wrote:
> The number's going up again though -- I think anything created since
> last week should marked 0.4 unless it's an important bug or very quick
> win.
>
> What if I put it this way -- if I marked all open 0.3 issues as 0.4
> right now, what would the ob
The number's going up again though -- I think anything created since
last week should marked 0.4 unless it's an important bug or very quick
win.
What if I put it this way -- if I marked all open 0.3 issues as 0.4
right now, what would the objections be?
On Fri, Feb 5, 2010 at 4:31 PM, Robin Ani
I just updated it here.
http://cwiki.apache.org/MAHOUT/creating-vectors-from-text.html
Lets rename/refactor the classes and get basic avro thing in for 0.3. So
that people who use gets a smooth upgrade to 0.4
Robin
On Fri, Feb 5, 2010 at 10:32 PM, Drew Farris wrote:
> On Fri, Feb 5, 2010 at 1
On Fri, Feb 5, 2010 at 11:53 AM, Jake Mannix wrote:
>
> Which is not to say that we shouldn't continue work on them, let's keep the
> patches going and up to date, let's just not worry about holding up 0.3
> until they're fully tested and checked in.
Yes absolutely. I'm also interested in hearin
Sounds great to me.
On Fri, Feb 5, 2010 at 11:50 AM, Ted Dunning wrote:
> Makes a lot of sense. Drew?
>
> On Fri, Feb 5, 2010 at 8:48 AM, Jake Mannix wrote:
>
>> So are we really planning on all this structured document stuff and Avro
>> for
>> 0.3? Can we just try and finish up what was alrea
On Fri, Feb 5, 2010 at 8:48 AM, Jake Mannix wrote:
> So are we really planning on all this structured document stuff and Avro
> for 0.3? Can we just try and finish up what was already scoped for 0.3 and
> have a quick turnaround for getting things which have only been really
> started worked on
Makes a lot of sense. Drew?
On Fri, Feb 5, 2010 at 8:48 AM, Jake Mannix wrote:
> So are we really planning on all this structured document stuff and Avro
> for
> 0.3? Can we just try and finish up what was already scoped for 0.3 and
> have
> a quick turnaround for getting things which have onl
So are we really planning on all this structured document stuff and Avro for
0.3? Can we just try and finish up what was already scoped for 0.3 and have
a quick turnaround for getting things which have only been really started
worked on in the past week or so for 0.4 sometime next month?
-jake
On Fri, Feb 5, 2010 at 11:17 AM, Ted Dunning wrote:
> I just marked the 0.1 and 0.2 releases as released (about time). This makes
> the JIRA road map feature more usable.
>
> See here for the live version of this summary:
> https://issues.apache.org/jira/browse/MAHOUT?report=com.atlassian.jira.pl
Yum Yum.
0.1 59 issues
0.2 66 issues
0.3 91 issues - 13 left
On Fri, Feb 5, 2010 at 9:47 PM, Ted Dunning wrote:
> I just marked the 0.1 and 0.2 releases as released (about time). This
> makes
> the JIRA road map feature more usable.
>
> See here for the live version of this summary:
>
> ht
I just marked the 0.1 and 0.2 releases as released (about time). This makes
the JIRA road map feature more usable.
See here for the live version of this summary:
https://issues.apache.org/jira/browse/MAHOUT?report=com.atlassian.jira.plugin.system.project:roadmap-panel
On Fri, Feb 5, 2010 at 3:16
Reviving this thread. Copy paste the whole thing as we move forward
Current Snapshot
Key Summary
> MAHOUT-221 Implementation of FP-Bonsai Pruning for fast pattern mining
>Done
> MAHOUT-227 Parallel SVM In Progress
> MAHOUT-240 Parallel version of Perceptron Little Progr
On Mon Jake Mannix wrote:
> On Mon, Jan 25, 2010 at 10:55 AM, Sean Owen wrote:
>
> > Agree that we should start planning 0.3, as it will take over a
> > month I bet to actually be ready.
> >
>
> +1 to releasing within a month or so.
+1 here as well. I think it would be great to reach a shorter
On Mon Ted Dunning wrote:
> 240 can be WONT-FIX'ed.
+1
> I think that Isabel may have something for 241.
Nothing that I see as ready to go into 0.3.
Isabel
On Mon Grant Ingersoll wrote:
> >> MAHOUT-231 Upgrade QM reports to use Clover 2.6
> >>
> >
> > No idea on this one.
>
> That should be independent of a release, I would think.
It is. What would be needed is adjusting our pom and the Hudson job
that builds the reports.
Isabel
On Mon, Jan 25, 2010 at 8:34 PM, Drew Farris wrote:
>
>> MAHOUT-215 Provide jars with mahout release.
>
> +1 working on this now.
A patch is now available for this in JIRA. Feedback appreciated.
Hi all,
I will do my best to get this in 0.3 release.
{quote}
> MAHOUT-232 Implementation of sequential SVM solver based on Pegasos
>
This patch looks to be progressing - it would be really nice to get it in.
{quote}
Cheers,
Zhendong
--
On Mon, Jan 25, 2010 at 5:34 PM, Drew Farris wrote:
>
>
> I'd like to get the LLR Collocation finder in there too, but we'll
> have to see how much time I have to work on that wrt to the release
> timeframe. Perhaps the simpler version that's available in the current
> patch if I don't get to the
On Mon, Jan 25, 2010 at 1:55 PM, Sean Owen wrote:
> MAHOUT-185 Add mahout shell script for easy launching of various
> algorithms
+1, if even because I hate trying to remember the command-line
arguments for mvn exec:java. It becomes much easier to write
documentation/examples if it is easy
On Jan 25, 2010, at 2:13 PM, Jake Mannix wrote:
>
>
>> MAHOUT-215 Provide jars with mahout release.
>>
>
> ++1 on this one getting in. "showstopper" I'd say.
Not sure it is a showstopper, but it is important.
>
>
>> MAHOUT-209 Add aggregate() methods for Vector
>>
>
> It woul
I am glad that I waited to read Jake's summary since it saved my typing and
agreeing with every one of his points.
The only difference I have is here:
> Key Summary
> MAHOUT-221 Implementation of FP-Bonsai Pruning for fast pattern
mining
> MAHOUT-227 Parallel SVM
> MAHOUT-240 P
On Mon, Jan 25, 2010 at 10:55 AM, Sean Owen wrote:
> Agree that we should start planning 0.3, as it will take over a month
> I bet to actually be ready.
>
+1 to releasing within a month or so.
> How about everyone take a moment to focus on what's marked for 0.3?
> for any issue that concerns y
omething in the central repo
>> with an ASL license and some primitive collections. What's the current
>> release thinking?
>>
>> p.s. I'll start on the math split tonight.
>>
>
collections. What's the current
> release thinking?
>
> p.s. I'll start on the math split tonight.
>
I would be very happy to see a release with the Colt collections
before we switch, just so that there is something in the central repo
with an ASL license and some primitive collections. What's the current
release thinking?
p.s. I'll start on the math split tonight.
29 matches
Mail list logo
