What does this mean? You mean make a 301-continuation ticket for 0.4, and reschedule the original 301 for 0.3? I could do that *if* 301 is in good shape by the time Hadoop is ready, but I don't want to reschedule it until it is.
-jake On Tue, Feb 23, 2010 at 9:57 AM, Ted Dunning <ted.dunn...@gmail.com> wrote: > WHat about a new follow-on JIRA so 301 can stay in the official release > notes? > > On Tue, Feb 23, 2010 at 9:40 AM, 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. > > > > > > -- > Ted Dunning, CTO > DeepDyve >
