GitHub user zjffdu opened a pull request:

    https://github.com/apache/zeppelin/pull/2760

    [WIP] ZEPPELIN-3196. Plugin framework for Zeppelin Engine

    ### What is this PR for?
    A few sentences describing the overall goals of the pull request's commits.
    First time? Check out the contributing guide - 
https://zeppelin.apache.org/contribution/contributions.html
    
    
    ### What type of PR is it?
    [Bug Fix | Improvement | Feature | Documentation | Hot Fix | Refactoring]
    
    ### Todos
    * [ ] - Task
    
    ### What is the Jira issue?
    * Open an issue on Jira https://issues.apache.org/jira/browse/ZEPPELIN/
    * Put link here, and add [ZEPPELIN-*Jira number*] in PR title, eg. 
[ZEPPELIN-533]
    
    ### How should this be tested?
    * First time? Setup Travis CI as described on 
https://zeppelin.apache.org/contribution/contributions.html#continuous-integration
    * Strongly recommended: add automated unit tests for any new or changed 
behavior
    * Outline any manual steps to test the PR here.
    
    ### Screenshots (if appropriate)
    
    ### Questions:
    * Does the licenses files need update?
    * Is there breaking changes for older versions?
    * Does this needs documentation?


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/zjffdu/zeppelin ZEPPELIN-3196

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/zeppelin/pull/2760.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #2760
    
----
commit ad3233ab4e6c670a9e1ddc275aed7b810caa22ac
Author: Jeff Zhang <zjffdu@...>
Date:   2018-01-31T11:46:44Z

    ZEPPELIN-3196. Plugin framework for Zeppelin Engine

----


---

Reply via email to