GitHub user minahlee opened a pull request:

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

    [WIP][ZEPPELIN-986] Create publish release script

    ### What is this PR for?
    This PR is to automate release publish to maven repository.
    We used to use maven-deploy-plugin and maven-release-plugin for release but 
somehow it didn't work well with Zeppelin so 0.5.5 and 0.5.6 haven't been 
published to maven repository.
    Publishing release to maven repository will eventaully help zeppelin to 
reduce binary package size by leading users to use Dynamic interpreter 
loading(#908).
    
    ### What type of PR is it?
    Infra
    
    ### What is the Jira issue?
    [ZEPPELIN-986](https://issues.apache.org/jira/browse/ZEPPELIN-986)
    
    ### Questions:
    * Does the licenses files need update? No
    * Is there breaking changes for older versions? No
    * Does this needs documentation? Yes, 
https://cwiki.apache.org/confluence/display/ZEPPELIN/Preparing+Zeppelin+Release 
will be updated accordingly once this pr is merged.


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

    $ git pull https://github.com/minahlee/zeppelin ZEPPELIN-986

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

    https://github.com/apache/zeppelin/pull/994.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 #994
    
----
commit e03e03ef0fd7e073c941871468627d4371d13888
Author: Mina Lee <mina...@apache.org>
Date:   2016-06-10T20:35:42Z

    Add maven publish release script

commit 488d98cc48f2ca335c4a11a1f413b76a59d42de8
Author: Mina Lee <mina...@apache.org>
Date:   2016-06-10T20:35:51Z

    Refactor create release script

----


---
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