Github user bzz commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/208#issuecomment-203234120
@elbamos It is possible to do exactly so, but then we will need to create a
new PR from that feature branch to master, in order to get it merged, right?
And this way, that PR will not be under your name (so tooling probably will
not pick it up on final merge), also ASF<->GH integration does not grant full
rights to committers either, i.e not sure that we will be able to create such
PR ->master, as we never tried. What I'm saying is - it might take some time to
figure that out, as this is a bit different from the regular process the
project followed before.
What do you think would be better?
- treat this branch as "Feature branch" and freeze it, making all CI work
on top of it (as PRs to your fork)
- or create a "feature branch" under apache repo, new PR -> master, and
PRs with CI work on top of that one
- or create a new "feature branch" under your repo and PRs for CI from
there
Let me know what you think!
I'm willing to help nailing down the pyspark tests failures - spark been
not reliably launched on CI can be the case indeed, but it is way too
"reproducible" - somehow if fails every single time, so it may be just some
very simple but un-obvious bug somewhere.
---
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.
---
