I think that we should do D. The primary action that we should take before then is to resolve trivial issues. For instance, MAHOUT-399 can be marked WONT_FIX.
[image: Bug]MAHOUT-399 <https://issues.apache.org/jira/browse/MAHOUT-399> <https://issues.apache.org/jira/browse/MAHOUT-399>Due Date: 25/Mar/11LDA on Mahout 0.3 does not converge to correct solution for overlapping pyramids toy problem. On Tue, May 22, 2012 at 6:30 PM, tom pierce <[email protected]> wrote: > +1 for D. Many of those seem like worthwhile improvements, and if a week > or so allows a few to get resolved, that seems like a good tradeoff to me. > > I'd be inclined to vote C (or maybe A) on 6/1, though. > > -t > > > > > On 05/22/2012 12:33 PM, Jeff Eastman wrote: > >> >> A - punt all non-critical issues to 0.8 >> B - punt all low priority issues to 0.8 and wait for the others to be >> resolved >> C - punt all open issues to 0.8 and get on with the release >> D - delay the target date for code freeze until 1 June and reassess then >> >> Jeff >> > >
