So to be an annoying voice of dissent... I'm going to keep iterating on MAHOUT-301, targetted for 0.4, and I will keep it in patch form (not checked in) _for now_... but if it can get its wrinkles ironed out before Hadoop gets its act together, I really think it should get committed to 0.3.
It's minimally invasive (one java file, and some config files, all additions (not changes), and then changes to the mahout shell script), and has the potential to really make repeatedly running our tools far easier than it currently is. -jake ps. if we are really doing a code freeze, can we make a dev branch (or more appropriately, make a 0.3 release branch, and allow continued development on trunk)? We don't really want to hold up on producing new stuff, do we? More more MORE! ;) On Tue, Feb 23, 2010 at 9:25 AM, Ted Dunning <ted.dunn...@gmail.com> wrote: > +1 to code freeze, waiting for hadoop release and testing the RC > > On Tue, Feb 23, 2010 at 8:38 AM, Isabel Drost <isa...@apache.org> wrote: > > > On Tue Grant Ingersoll <gsing...@apache.org> wrote: > > > On Feb 23, 2010, at 9:18 AM, Sean Owen wrote: > > > > > > > It does look imminent. As much as I don't like holding out longer, > > > > and indefinitely, for this release, somehow I'd also really like to > > > > link to the latest/greatest and official Hadoop release. > > > > > > > > Let's try to be good about sticking to the code freeze -- good > > > > chance to focus on polish -- and if 0.20.2 isn't out by end of > > > > week, revisit this. > > > > > > +1. We might as well upgrade to the RC, too, by adding it as a > > > dependency. > > > > +1 (to both proposals) > > > > Isabel > > > > > > -- > Ted Dunning, CTO > DeepDyve >
