https://issues.apache.org/jira/browse/BIGTOP-114 and https://issues.apache.org/jira/browse/BIGTOP-115 are pending review. https://issues.apache.org/jira/browse/BIGTOP-34 has been waiting for review forever, and I didn't really know what to do there in the first place. =) I think https://issues.apache.org/jira/browse/BIGTOP-51 is done enough for here. https://issues.apache.org/jira/browse/BIGTOP-89 is kind of unresolvable without patching the example scripts.
A. On Tue, Oct 18, 2011 at 11:55 AM, Bruno Mahé <[email protected]> wrote: > On 10/17/2011 02:31 PM, Roman Shaposhnik wrote: > > Fellow Bigtoppers, > > > > even though 0.1.0 was only ~2 month ago it seems that we've got > > plenty of good stuff in our trunk waiting for 0.2.0. I would like to > propose > > that we shoot for 0.2.0 to be available first week of November 2011 > > and that it includes the following Hadoop stack components (note > > that we will NOT be bumping version of Hadoop): > > https://issues.apache.org/jira/browse/BIGTOP-28 > > On top of that, I propose that we make iTest validation be part of the > > release criteria for 0.2.0. > > > > Now, all together we have 21 issues assigned to 0.2.0: > > > https://issues.apache.org/jira/secure/IssueNavigator.jspa?sorter/field=assignee&sorter/order=ASC > > > > Andrew has 6 assigned to him, Bruno has 1 and it seems that I've got > > the rest of them. I would appreciate if you guys can take a look > > at the ones assigned to you and let me know if you are comfortable > > fixing them this week or whether they can be punted to 0.3.0. > > > > Thanks, > > Roman. > > I definitely agree. > I would really like to use the coming weeks to spend more time on > testing the stack. BIGTOP-119 really scared me. > Would a test day or similar event be helpful? > >
