GitHub user AhyoungRyu opened a pull request:

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

    [MINOR] Update outdated contents in zeppelin-distribution/*.md files

    ### What is this PR for?
    It seems some outdated contents are remained in 
`zeppelin-distribution/*.md` files. 
    e.g. `Zeppelin CLI`, `Zeppelin project(old name of Apache Zeppelin)`
    
    If there are more contents which need to be updated(removed or put it 
back), please let me know.
    
    
    ### What type of PR is it?
    Documentation
    
    ### What is the Jira issue?
    Since it's so minor update, I didn't create Jira issue for this :)
    
    ### How should this be tested?
    no need to be tested i think
    
    ### Screenshots (if appropriate)
     - `zeppelin-distribution/build-infrastructure.md`
      - Before
    <img width="935" alt="screen shot 2016-08-10 at 10 10 01 pm" 
src="https://cloud.githubusercontent.com/assets/10060731/17554895/1c56a0ee-5f48-11e6-96ce-28070635b4f2.png";>
    
      - After
    <img width="704" alt="screen shot 2016-08-10 at 10 06 38 pm" 
src="https://cloud.githubusercontent.com/assets/10060731/17554893/16cd2fc6-5f48-11e6-8194-cc8011b0ddb8.png";>
    
    
    ### Questions:
    * Does the licenses files need update? no
    * Is there breaking changes for older versions? no
    * Does this needs documentation? no
    


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

    $ git pull https://github.com/AhyoungRyu/zeppelin 
update/distribution-outdated-file

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

    https://github.com/apache/zeppelin/pull/1314.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 #1314
    
----
commit 065622d2439f2f38154bb89b1bf2a1aeeeb13f7b
Author: AhyoungRyu <[email protected]>
Date:   2016-08-10T13:04:50Z

    Update outdated contents *.md files under zeppelin-distribution/

----


---
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 [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to