Github user bzz commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/208#issuecomment-203224008
@elbamos I see. The problem is that such intentions (removing not
permanently) are not obvious for a reviewers, as they just do not know and
assume that current state is the one you want to get merged.
Experiments are very good, but if you conduct them in a separate from this
PR branch (but on top this work, same way as elbamos/Zeppelin-With-R#12) - it
would simplify the final review of this PR a lot, making things faster.
I.e tests generating spurious failures must be proven to do so on other
PRs\branches and indeed must be improved or taken out, but all this should
happen outside of the scope of this particular PR, keeping things small and
simple. (I.e if one test is found to be guilty, the PR fixing\removing it must
be merged first and then this one rebased on top)
That is what I meant. Does it make sense?
---
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.
---
