Github user Leemoonsoo commented on the pull request:

    https://github.com/apache/incubator-zeppelin/pull/702#issuecomment-202179148
  
    > It is not at all a surprise that you would propose to merge 702---a few 
hours after I asked for community involvement on another PR, where you objected.
    
    False.
    No one objected community involvement on PR 
https://github.com/apache/incubator-zeppelin/pull/789. In fact, I suggested you 
create discussion thread. And you seems you did. great job :smiley: 
    
    
    > At the moment, this PR has zero adoption. You made a major change in its 
architecture a day ago that no-one has had a chance to try out.
    
    Adoption is not a requirement of code contribution. Most code contribution 
merges with 0 adoption.
    
    > And it has zero tests --- because the CI issue still isn't solved, 
they've been replaced by tests that don't cover the PRs functionality and don't 
even test if it can connect to R or Spark. 
    
    This PR includes an integration test which verifies Zeppelin - RInterpreter 
- R - Spark cluster connection.
    While CI is not green, i hope @echarles can trigger it again and see if 
it's passing.
    
    > This is absolutely the opposite of the consensus the community has 
repeatedly reached about the R issue.
    > Will you be abiding by the community's consensus or do we really need to 
start a seventh discussion about this on the mailing list?
    
    I think this PR is not against community consensus. Please check this 
thread 
http://apache-zeppelin-incubating-dev-mailing-list.75694.x6.nabble.com/R-interpreter-in-Zeppelin-further-steps-tp6967.html



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to