I am stuck out of town until early next week. I'd planned on spending some time looking at m-1500 when I get back.
Andy Sent from my Verizon Wireless 4G LTE smartphone <div>-------- Original message --------</div><div>From: "Dmitriy Lyubimov (JIRA)" <[email protected]> </div><div>Date:07/31/2014 12:44 PM (GMT-05:00) </div><div>To: [email protected] </div><div>Subject: [jira] [Commented] (MAHOUT-1500) H2O integration </div><div> </div> [ https://issues.apache.org/jira/browse/MAHOUT-1500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14081093#comment-14081093 ] Dmitriy Lyubimov commented on MAHOUT-1500: ------------------------------------------ The reason additional review on github is needed is because i only spent ~5 minutes eyeballing less than 10% of the code which spawned 5 or so notes and subsequent fixes. In that sense, help is needed. Surely, benefits of cross peer code review should really require no specific justification. This is code review on github (which is our reviewboard replacement) -- you just need to look at the code, poke it if possible, leave suggestions, or just say "ship it". I know, reviewboard was pain to use, but github PRs are so easy, so there's practically no pretext left not to do it as much as possible. Which begs the question. All these people who apparently said "ship it" on github, excluding 0xdata review, produced exactly 0 code notes. Either review were even more superficial than mine, or it is the most impeccable code patch in the history of the project. > H2O integration > --------------- > > Key: MAHOUT-1500 > URL: https://issues.apache.org/jira/browse/MAHOUT-1500 > Project: Mahout > Issue Type: Improvement > Reporter: Anand Avati > Fix For: 1.0 > > > Provide H2O backend for the Mahout DSL -- This message was sent by Atlassian JIRA (v6.2#6252)
