GitHub user AhyoungRyu reopened a pull request:

    https://github.com/apache/incubator-zeppelin/pull/953

    ZEPPELIN-947: Change docs link to point the same Zeppelin version

    ### What is this PR for?
    Currently, Zeppelin documentation link in Zeppelin home is pointing to 
http://zeppelin.apache.org/docs/latest/index.html. But maybe some people is not 
using the latest version. So the link should point to the same Zeppelin version 
that user is using now.
    
    I just change the `latest` -> `{{zeppelinVersion}}`
    
    ### What type of PR is it?
    Improvement
    
    ### Todos
    
    ### What is the Jira issue?
    [ZEPPELIN-947](https://issues.apache.org/jira/browse/ZEPPELIN-947)
    
    ### How should this be tested?
    1. After applying this patch and browse Zeppelin home. 
    2. Just click `Zeppelin Documentation` link in here 
    <img width="357" alt="screen shot 2016-06-02 at 1 11 17 pm" 
src="https://cloud.githubusercontent.com/assets/10060731/15759461/8b69ee5c-28c3-11e6-8181-2fc2978c0297.png";>
    
    ### Screenshots (if appropriate)
    
    ### 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/incubator-zeppelin ZEPPELIN-947

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

    https://github.com/apache/incubator-zeppelin/pull/953.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 #953
    
----
commit 4c7206707ecf2d5ba4a507b78a24a4e7090e9548
Author: AhyoungRyu <fbdkdu...@hanmail.net>
Date:   2016-06-02T20:09:19Z

    ZEPPELIN-947: Change docs link to point the same Zeppelin version

----


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