You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zeppelin.apache.org by beneficial02 <gi...@git.apache.org> on 2017/08/15 06:14:48 UTC
[GitHub] zeppelin pull request #2530: [ZEPPELIN-2853] Change the order of contents in...
GitHub user beneficial02 opened a pull request:
https://github.com/apache/zeppelin/pull/2530
[ZEPPELIN-2853] Change the order of contents in index document.
### What is this PR for?
To change the order of content in index documentation. Now the last two contents is "External Resources" and "Available Interpreters". This PR change the order to "Available Interpreters" and "External Resources".
### What type of PR is it?
[Documentation]
### What is the Jira issue?
https://issues.apache.org/jira/browse/ZEPPELIN-2853
### How should this be tested?
1. Read the doc
### Screenshots (if appropriate)
Before
<img width="726" alt="screen shot 2017-08-15 at 3 08 14 pm" src="https://user-images.githubusercontent.com/19610222/29304040-d9f9adac-81cb-11e7-9aa3-0a325511e267.png">
After
<img width="615" alt="screen shot 2017-08-15 at 3 04 44 pm" src="https://user-images.githubusercontent.com/19610222/29304001-a26fca6a-81cb-11e7-8cf2-be10eef781d9.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/beneficial02/zeppelin feature/change_doc_order
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/zeppelin/pull/2530.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 #2530
----
commit 68ab9a50f3a7c8616231a0da31c7dbf21c8f7f68
Author: Loun Lee <be...@gmail.com>
Date: 2017-08-15T05:52:30Z
feature: change the order of doc content
----
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] zeppelin issue #2530: [ZEPPELIN-2853] Change the order of contents in index ...
Posted by Leemoonsoo <gi...@git.apache.org>.
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/2530
Thanks @beneficial02 for nice improvement on doc.
LGTM and merge to master if no further comment.
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] zeppelin pull request #2530: [ZEPPELIN-2853] Change the order of contents in...
Posted by beneficial02 <gi...@git.apache.org>.
GitHub user beneficial02 reopened a pull request:
https://github.com/apache/zeppelin/pull/2530
[ZEPPELIN-2853] Change the order of contents in index document.
### What is this PR for?
To change the order of content in index documentation. Now the last two contents is "External Resources" and "Available Interpreters". This PR change the order to "Available Interpreters" and "External Resources".
### What type of PR is it?
[Documentation]
### What is the Jira issue?
https://issues.apache.org/jira/browse/ZEPPELIN-2853
### How should this be tested?
1. Read the doc
### Screenshots (if appropriate)
Before
<img width="726" alt="screen shot 2017-08-15 at 3 08 14 pm" src="https://user-images.githubusercontent.com/19610222/29304040-d9f9adac-81cb-11e7-9aa3-0a325511e267.png">
After
<img width="615" alt="screen shot 2017-08-15 at 3 04 44 pm" src="https://user-images.githubusercontent.com/19610222/29304001-a26fca6a-81cb-11e7-8cf2-be10eef781d9.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/beneficial02/zeppelin feature/change_doc_order
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/zeppelin/pull/2530.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 #2530
----
commit 10a7172d905a960f10de3501c4abf4fd4978ac83
Author: Loun Lee <be...@gmail.com>
Date: 2017-08-15T05:52:30Z
feature: change the order of doc content
There was a Travis error so amend last commit.
----
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] zeppelin pull request #2530: [ZEPPELIN-2853] Change the order of contents in...
Posted by beneficial02 <gi...@git.apache.org>.
Github user beneficial02 closed the pull request at:
https://github.com/apache/zeppelin/pull/2530
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] zeppelin pull request #2530: [ZEPPELIN-2853] Change the order of contents in...
Posted by asfgit <gi...@git.apache.org>.
Github user asfgit closed the pull request at:
https://github.com/apache/zeppelin/pull/2530
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---