I say use your judgment. If you feel confident enough for it to be enshrined for about 3 months in an official release, check it in. Soon we will indeed want a proper release branch. This time it shouldn't be more than a few days, and, probably good discipline to force everyone to do nothing but documentation and test improvements for that time.
On Tue, Feb 23, 2010 at 5:40 PM, Jake Mannix <jake.man...@gmail.com> wrote: > 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! ;) >
