You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zeppelin.apache.org by AhyoungRyu <gi...@git.apache.org> on 2016/06/17 05:29:49 UTC
[GitHub] zeppelin pull request #1031: [ZEPPELIN-1018] Apply auto "Table of Contents" ...
GitHub user AhyoungRyu opened a pull request:
https://github.com/apache/zeppelin/pull/1031
[ZEPPELIN-1018] Apply auto "Table of Contents" generator to Zeppelin docs website
### What is this PR for?
I added auto TOC(Table of Contents) generator for Zeppelin documentation website. TOC can help people looking through whole contents at a glance and finding what they want quickly.
I just added `<div id="toc"></div>` to the each documentation header. [`toc`](https://github.com/apache/zeppelin/compare/master...AhyoungRyu:ZEPPELIN-1018?expand=1#diff-85af09fb498a5667ea455391533f945dR3) recognize `<h2>` & `<h3>` as a title in the docs and it automatically generate TOC. So I set a rule for this work. (I'll write this rule on `docs/CONTRIBUTING.md` or [docs/howtocontributewebsite](https://zeppelin.apache.org/docs/0.6.0-SNAPSHOT/development/howtocontributewebsite.html)).
```
# Level-1 Heading <- Use only for the main title of the page
## Level-2 Heading <- Start with this one
### Level-3 heading <- Only use this one for child of Level-2
toc only recognize Level-2 & Level-3
```
Please see the below attached screenshot image.
### What type of PR is it?
Improvement & Documentation
### Todos
* [x] - Add TOC generator
* [x] - Apply TOC(`<div id="toc"></div>`) to every documentation and reorganize each headers(apply the above rule)
* [x] - Fix some broken code block in several docs
* [ ] - Apply TOC to `r.md` (Currently R docs has some duplicated info since [this one](https://github.com/apache/zeppelin/commit/d5e87fb8ba98f08db5b0a4995104ce19f182c678) and [this one](https://github.com/apache/zeppelin/commit/7d6cc7e99154e2d337c11fdf8be1a874ed3e9ada) )
* [ ] - Apply TOC to `install.md` after #1010 merged
### What is the Jira issue?
[ZEPPELIN-1018](https://issues.apache.org/jira/browse/ZEPPELIN-1018)
### How should this be tested?
1. Apply this patch and build `docs/` with [this guide](https://github.com/apache/zeppelin/tree/master/docs#build-documentation)
2. Visit some docs page. Then you can see TOC in the header of page.
### Screenshots (if appropriate)
- Automatically generated TOC in Spark interpreter docs page
<img width="831" alt="screen shot 2016-06-16 at 9 37 18 pm" src="https://cloud.githubusercontent.com/assets/10060731/16140902/945b9c7a-340a-11e6-91f3-b6174738bed0.png">
### Questions:
* Does the licenses files need update?
No. Actually I used [jekyll-table-of-contents#copyright](https://github.com/ghiculescu/jekyll-table-of-contents#copyright). But I don't need to add a license for this :)
* Is there breaking changes for older versions? No
* Does this needs documentation? Maybe
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/AhyoungRyu/incubator-zeppelin ZEPPELIN-1018
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/zeppelin/pull/1031.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 #1031
----
commit 162193a8a57475480898ee84290e83d36462febe
Author: AhyoungRyu <fb...@hanmail.net>
Date: 2016-06-17T01:10:06Z
Add toc.js for auto generating TOC
commit ba57b519c3f12bc61ecbb80b0d0c06158c08c485
Author: AhyoungRyu <fb...@hanmail.net>
Date: 2016-06-17T02:40:17Z
Change toc configuration
commit 711ab09f8dd6c056dedf3fb4c8bd43633fa3e8d2
Author: AhyoungRyu <fb...@hanmail.net>
Date: 2016-06-17T02:41:49Z
Apply auto TOC to all of docs under docs/security/
commit c9848c47ba5963db2b1946260f251fe3288675fe
Author: AhyoungRyu <fb...@hanmail.net>
Date: 2016-06-17T02:42:17Z
Apply auto TOC to all of docs under docs/interpreter/
commit 796530e350b76a5ed36a4a6e516cd2eee0248bcc
Author: AhyoungRyu <fb...@hanmail.net>
Date: 2016-06-17T02:42:32Z
Apply auto TOC to all of docs under docs/development/
commit 002ec825e7f7edb5f88372e298501c2bffcbdbf6
Author: AhyoungRyu <fb...@hanmail.net>
Date: 2016-06-17T02:42:46Z
Apply auto TOC to all of docs under docs/manual/
commit a79fef6ec27ffdf5abf623cc1580301b5fed3d02
Author: AhyoungRyu <fb...@hanmail.net>
Date: 2016-06-17T02:42:59Z
Apply auto TOC to all of docs under docs/rest-api/
commit 41fbdeb1418a4db91b9362586e002608e135844b
Author: AhyoungRyu <fb...@hanmail.net>
Date: 2016-06-17T02:43:15Z
Apply auto TOC to all of docs under docs/displaysystem/
commit 3f9fd674c1b1b86a04c4d4b03f636a2af1acf651
Author: AhyoungRyu <fb...@hanmail.net>
Date: 2016-06-17T02:43:28Z
Apply auto TOC to all of docs under docs/install/
commit f62fb1b77fd32b3e850c1aee166f4cfcebba094e
Author: AhyoungRyu <fb...@hanmail.net>
Date: 2016-06-17T02:43:40Z
Apply auto TOC to all of docs under docs/quickstart/
commit 17ff694d93e4871e69dd667f293b1bf6b38c5e2f
Author: AhyoungRyu <fb...@hanmail.net>
Date: 2016-06-17T02:44:01Z
Apply auto TOC to all of docs under docs/storage/
commit 0315d5c3901d54ba3ce85401665a6a2f4f42799f
Author: AhyoungRyu <fb...@hanmail.net>
Date: 2016-06-17T02:44:47Z
Resize TOC tab indent
----
---
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 #1031: [ZEPPELIN-1018] Apply auto "Table of Contents" ...
Posted by AhyoungRyu <gi...@git.apache.org>.
Github user AhyoungRyu closed the pull request at:
https://github.com/apache/zeppelin/pull/1031
---
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 #1031: [ZEPPELIN-1018] Apply auto "Table of Contents" generat...
Posted by AhyoungRyu <gi...@git.apache.org>.
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1031
TODO list is done for now. This PR has big changes in overall documentation, but most of them is for reorganization the title & header in each docs for more well-organized TOC.
So ready for review :)
---
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 #1031: [ZEPPELIN-1018] Apply auto "Table of Contents" ...
Posted by asfgit <gi...@git.apache.org>.
Github user asfgit closed the pull request at:
https://github.com/apache/zeppelin/pull/1031
---
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 #1031: [ZEPPELIN-1018] Apply auto "Table of Contents" generat...
Posted by minahlee <gi...@git.apache.org>.
Github user minahlee commented on the issue:
https://github.com/apache/zeppelin/pull/1031
It looks great to me. Thanks for improving document
---
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 #1031: [ZEPPELIN-1018] Apply auto "Table of Contents" generat...
Posted by AhyoungRyu <gi...@git.apache.org>.
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1031
@felixcheung Really appreciate your feedback :) I just addressed them.
---
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 #1031: [ZEPPELIN-1018] Apply auto "Table of Contents" generat...
Posted by AhyoungRyu <gi...@git.apache.org>.
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1031
@minahlee My pleasure, thanks :)
---
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 #1031: [ZEPPELIN-1018] Apply auto "Table of Contents" generat...
Posted by AhyoungRyu <gi...@git.apache.org>.
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1031
But CI failure is irrelevant with this change i think. There are 2 errors like below.
#### 1.
Running org.apache.zeppelin.python.PythonInterpreterTest
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [jar:file:/home/travis/build/apache/zeppelin/zeppelin-interpreter/target/zeppelin-interpreter-0.6.0-SNAPSHOT.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [jar:file:/home/travis/build/apache/zeppelin/zeppelin-interpreter/target/lib/slf4j-log4j12-1.7.10.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [jar:file:/home/travis/.m2/repository/org/slf4j/slf4j-log4j12/1.7.10/slf4j-log4j12-1.7.10.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory]
log4j:WARN No appenders could be found for logger (org.apache.zeppelin.interpreter.Interpreter).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.
Tests run: 5, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.434 sec <<< FAILURE! - in org.apache.zeppelin.python.PythonInterpreterTest
testClose(org.apache.zeppelin.python.PythonInterpreterTest) Time elapsed: 0.317 sec <<< FAILURE!
java.lang.AssertionError: null
at org.junit.Assert.fail(Assert.java:86)
at org.junit.Assert.assertTrue(Assert.java:41)
at org.junit.Assert.assertFalse(Assert.java:64)
at org.junit.Assert.assertFalse(Assert.java:74)
at org.apache.zeppelin.python.PythonInterpreterTest.testClose(PythonInterpreterTest.java:170)
Results :
Failed tests:
PythonInterpreterTest.testClose:170 null
Tests run: 5, Failures: 1, Errors: 0, Skipped: 0
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] Zeppelin ........................................... SUCCESS [ 10.254 s]
[INFO] Zeppelin: Interpreter .............................. SUCCESS [01:55 min]
[INFO] Zeppelin: Zengine .................................. SUCCESS [ 24.280 s]
[INFO] Zeppelin: Display system apis ...................... SUCCESS [ 2.810 s]
[INFO] Zeppelin: Spark dependencies ....................... SUCCESS [ 42.031 s]
[INFO] Zeppelin: Spark .................................... SUCCESS [01:47 min]
[INFO] Zeppelin: Markdown interpreter ..................... SUCCESS [ 0.634 s]
[INFO] Zeppelin: Angular interpreter ...................... SUCCESS [ 0.285 s]
[INFO] Zeppelin: Shell interpreter ........................ SUCCESS [ 0.391 s]
[INFO] Zeppelin: Livy interpreter ......................... SUCCESS [ 0.612 s]
[INFO] Zeppelin: HBase interpreter ........................ SUCCESS [ 9.700 s]
[INFO] Zeppelin: PostgreSQL interpreter ................... SUCCESS [ 1.399 s]
[INFO] Zeppelin: JDBC interpreter ......................... SUCCESS [ 2.255 s]
[INFO] Zeppelin: File System Interpreters ................. SUCCESS [ 1.872 s]
[INFO] Zeppelin: Flink .................................... SUCCESS [ 19.149 s]
[INFO] Zeppelin: Apache Ignite interpreter ................ SUCCESS [ 22.431 s]
[INFO] Zeppelin: Kylin interpreter ........................ SUCCESS [ 0.937 s]
[INFO] Zeppelin: Python interpreter ....................... FAILURE [ 1.325 s]
[INFO] Zeppelin: Lens interpreter ......................... SKIPPED
[INFO] Zeppelin: Apache Cassandra interpreter ............. SKIPPED
[INFO] Zeppelin: Elasticsearch interpreter ................ SKIPPED
[INFO] Zeppelin: Alluxio interpreter ...................... SKIPPED
[INFO] Zeppelin: web Application .......................... SKIPPED
[INFO] Zeppelin: Server ................................... SKIPPED
[INFO] Zeppelin: Packaging distribution ................... SKIPPED
[INFO] Zeppelin: R Interpreter ............................ SKIPPED
[INFO] Zeppelin: Scalding interpreter ..................... SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 06:03 min
[INFO] Finished at: 2016-06-21T07:17:53+00:00
[INFO] Final Memory: 59M/357M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.17:test (default-test) on project zeppelin-python: There are test failures.
[ERROR]
[ERROR] Please refer to /home/travis/build/apache/zeppelin/python/target/surefire-reports for the individual test results.
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn <goals> -rf :zeppelin-python
#### 2. Selenium Test error
Results :
Failed tests:
ParagraphActionsIT.testTitleButton:350 After Show Title : The title field contains
Expected: "Untitled"
but: was ""
ParagraphActionsIT.testTitleButton:360 After Hide Title : The title field contains
Expected: ""
but: was "Untitled"
ParagraphActionsIT.testRemoveButton:161 After Remove : Number of paragraphs are
Expected: <2>
but: was <1>
Tests run: 16, Failures: 3, Errors: 0, Skipped: 0
[INFO]
[INFO] --- scalatest-maven-plugin:1.0:test (test) @ zeppelin-server ---
[36mDiscovery starting.[0m
Jun 21, 2016 7:18:12 AM org.openqa.selenium.safari.SafariDriverServer start
INFO: Server started on port 10154
Jun 21, 2016 7:18:12 AM org.openqa.selenium.safari.SafariDriverCommandExecutor stop
INFO: Shutting down
Jun 21, 2016 7:18:12 AM org.openqa.selenium.safari.SafariDriverCommandExecutor stop
INFO: Stopping server
Jun 21, 2016 7:18:12 AM org.openqa.selenium.safari.SafariDriverServer stop
INFO: Stopping server
Jun 21, 2016 7:18:12 AM org.openqa.selenium.safari.SafariDriverCommandExecutor stop
INFO: Shutdown complete
[36mDiscovery completed in 3 seconds, 135 milliseconds.[0m
[36mRun starting. Expected test count is: 1[0m
Zeppelin is already running
[32mWelcomePageSuite:[0m
[32m- Welcome sign is correct[0m
Zeppelin stop [60G[[1;32m OK [0;39m]
[36mRun completed in 12 seconds, 44 milliseconds.[0m
[36mTotal number of tests run: 1[0m
[36mSuites: completed 3, aborted 0[0m
[36mTests: succeeded 1, failed 0, canceled 0, ignored 0, pending 0[0m
[32mAll tests passed.[0m
[INFO]
[INFO] --- maven-antrun-plugin:1.7:run (stop-zeppelin) @ zeppelin-server ---
[INFO] Executing tasks
main:
[exec] Zeppelin is not running
[INFO] Executed tasks
[INFO]
[INFO] --- apache-rat-plugin:0.11:check (verify.rat) @ zeppelin-server ---
[INFO] 51 implicit excludes (use -debug for more details).
[INFO] Exclude: **/.idea/
[INFO] Exclude: **/*.iml
[INFO] Exclude: .git/
[INFO] Exclude: .gitignore
[INFO] Exclude: **/.settings/*
[INFO] Exclude: **/.classpath
[INFO] Exclude: **/.project
[INFO] Exclude: **/target/**
[INFO] Exclude: **/derby.log
[INFO] Exclude: **/metastore_db/
[INFO] Exclude: **/README.md
[INFO] Exclude: src/test/java/com/webautomation/*
[INFO] 60 resources included (use -debug for more details)
[INFO] Rat check: Summary of files. Unapproved: 0 unknown: 0 generated: 0 approved: 60 licence.
[INFO]
[INFO] --- maven-failsafe-plugin:2.16:verify (default) @ zeppelin-server ---
[INFO] Failsafe report directory: /home/travis/build/apache/zeppelin/zeppelin-server/target/failsafe-reports
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] Zeppelin: Interpreter .............................. SUCCESS [ 21.471 s]
[INFO] Zeppelin: Zengine .................................. SUCCESS [ 5.803 s]
[INFO] Zeppelin: Display system apis ...................... SUCCESS [ 3.944 s]
[INFO] Zeppelin: Spark dependencies ....................... SUCCESS [ 37.600 s]
[INFO] Zeppelin: Spark .................................... SUCCESS [ 4.322 s]
[INFO] Zeppelin: Server ................................... FAILURE [07:21 min]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 08:35 min
[INFO] Finished at: 2016-06-21T07:18:25+00:00
[INFO] Final Memory: 47M/337M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-failsafe-plugin:2.16:verify (default) on project zeppelin-server: There are test failures.
[ERROR]
[ERROR] Please refer to /home/travis/build/apache/zeppelin/zeppelin-server/target/failsafe-reports for the individual test results.
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn <goals> -rf :zeppelin-server
Are they known errors?
---
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 #1031: [ZEPPELIN-1018] Apply auto "Table of Contents" ...
Posted by AhyoungRyu <gi...@git.apache.org>.
GitHub user AhyoungRyu reopened a pull request:
https://github.com/apache/zeppelin/pull/1031
[ZEPPELIN-1018] Apply auto "Table of Contents" generator to Zeppelin docs website
### What is this PR for?
I added auto TOC(Table of Contents) generator for Zeppelin documentation website. TOC can help people looking through whole contents at a glance and finding what they want quickly.
I just added `<div id="toc"></div>` to the each documentation header. [`toc`](https://github.com/apache/zeppelin/compare/master...AhyoungRyu:ZEPPELIN-1018?expand=1#diff-85af09fb498a5667ea455391533f945dR3) recognize `<h2>` & `<h3>` as a title in the docs and it automatically generate TOC. So I set a rule for this work. (I'll write this rule on `docs/CONTRIBUTING.md` or [docs/howtocontributewebsite](https://zeppelin.apache.org/docs/0.6.0-SNAPSHOT/development/howtocontributewebsite.html)).
```
# Level-1 Heading <- Use only for the main title of the page
## Level-2 Heading <- Start with this one
### Level-3 heading <- Only use this one for child of Level-2
toc only recognize Level-2 & Level-3
```
Please see the below attached screenshot image.
### What type of PR is it?
Improvement & Documentation
### Todos
* [x] - Add TOC generator
* [x] - Apply TOC(`<div id="toc"></div>`) to every documentation and reorganize each headers(apply the above rule)
* [x] - Fix some broken code block in several docs
* [x] - Apply TOC to `r.md` (Currently R docs has some duplicated info since [this one](https://github.com/apache/zeppelin/commit/d5e87fb8ba98f08db5b0a4995104ce19f182c678) and [this one](https://github.com/apache/zeppelin/commit/7d6cc7e99154e2d337c11fdf8be1a874ed3e9ada) )
* [x] - Apply TOC to `install.md` after #1010 merged
### What is the Jira issue?
[ZEPPELIN-1018](https://issues.apache.org/jira/browse/ZEPPELIN-1018)
### How should this be tested?
1. Apply this patch and build `docs/` with [this guide](https://github.com/apache/zeppelin/tree/master/docs#build-documentation)
2. Visit some docs page. Then you can see TOC in the header of page.
### Screenshots (if appropriate)
- Automatically generated TOC in Spark interpreter docs page
<img width="831" alt="screen shot 2016-06-16 at 9 37 18 pm" src="https://cloud.githubusercontent.com/assets/10060731/16140902/945b9c7a-340a-11e6-91f3-b6174738bed0.png">
### Questions:
* Does the licenses files need update?
No. Actually I used [jekyll-table-of-contents#copyright](https://github.com/ghiculescu/jekyll-table-of-contents#copyright). But I don't need to add a license for this :)
* Is there breaking changes for older versions? No
* Does this needs documentation? Maybe
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/AhyoungRyu/incubator-zeppelin ZEPPELIN-1018
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/zeppelin/pull/1031.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 #1031
----
commit 6c44ca9e0764857d3eb168290be0c1426cf35a32
Author: AhyoungRyu <fb...@hanmail.net>
Date: 2016-06-17T01:10:06Z
Add toc.js for auto generating TOC
commit 36aeecb1d95d85802ccf9a1e3aac11ba264ddee1
Author: AhyoungRyu <fb...@hanmail.net>
Date: 2016-06-17T02:40:17Z
Change toc configuration
commit 03b3cb5a3846ed5f72e6bbaa3e50ffb42582ba2f
Author: AhyoungRyu <fb...@hanmail.net>
Date: 2016-06-17T02:41:49Z
Apply auto TOC to all of docs under docs/security/
commit 8ce20fede41e23d14b56669f6be23b8463c215eb
Author: AhyoungRyu <fb...@hanmail.net>
Date: 2016-06-17T02:42:17Z
Apply auto TOC to all of docs under docs/interpreter/
commit 7630053c1e6cac6cb8d3c37954eb442fb7c02dd4
Author: AhyoungRyu <fb...@hanmail.net>
Date: 2016-06-17T02:42:32Z
Apply auto TOC to all of docs under docs/development/
commit 62edb9de146485c82c6b52a0ad33ff022fa0ad39
Author: AhyoungRyu <fb...@hanmail.net>
Date: 2016-06-17T02:42:46Z
Apply auto TOC to all of docs under docs/manual/
commit fe5e6abe6005b12ae02c9d0c148f6c72990d98e5
Author: AhyoungRyu <fb...@hanmail.net>
Date: 2016-06-17T02:42:59Z
Apply auto TOC to all of docs under docs/rest-api/
commit 851d42ee12b8b89515969cd779c5e807a17f3274
Author: AhyoungRyu <fb...@hanmail.net>
Date: 2016-06-17T02:43:15Z
Apply auto TOC to all of docs under docs/displaysystem/
commit fcc66d2efd711b1b86ee93f51428445c319fb7c2
Author: AhyoungRyu <fb...@hanmail.net>
Date: 2016-06-17T02:43:28Z
Apply auto TOC to all of docs under docs/install/
commit 7e9bd0d2342b9bab5b2e8d811210e379a8681ba4
Author: AhyoungRyu <fb...@hanmail.net>
Date: 2016-06-17T02:43:40Z
Apply auto TOC to all of docs under docs/quickstart/
commit 4a0a07a4ad18d3fdd189a0f5e5cec18f5d7c9c5a
Author: AhyoungRyu <fb...@hanmail.net>
Date: 2016-06-17T02:44:01Z
Apply auto TOC to all of docs under docs/storage/
commit 7474d4db9df57d05faed415476098b34ac2bdf49
Author: AhyoungRyu <fb...@hanmail.net>
Date: 2016-06-17T02:44:47Z
Resize TOC tab indent
commit 6a25bf042d0e2274528624aa51fffe6ef41d112e
Author: AhyoungRyu <fb...@hanmail.net>
Date: 2016-06-17T07:59:56Z
Address @felixcheung feedback
commit a7143ce91f75c61d0e4f5cf2f8051c5d7c840eaa
Author: AhyoungRyu <fb...@hanmail.net>
Date: 2016-06-20T08:22:21Z
Apply auto generated toc to install.md
commit 02205169782104669c896250299d9d2cce463aae
Author: AhyoungRyu <fb...@hanmail.net>
Date: 2016-06-20T18:53:39Z
Exclude toc.js from pom.xml
commit 41214e6b03a51a021c5cd6f7ce74a1af9b0436ef
Author: AhyoungRyu <fb...@hanmail.net>
Date: 2016-06-21T06:04:17Z
Remove duplicated info in r.md & apply toc
commit 323890ea03f0a53bac01a4f763fdc33df6bcdd8b
Author: AhyoungRyu <fb...@hanmail.net>
Date: 2016-06-21T06:05:41Z
Move interpreter/screenshot/ -> asset/../img/docs-img/
commit 8433b9ad9f71abab47d1d6ed6a3ae5840944a40e
Author: AhyoungRyu <fb...@hanmail.net>
Date: 2016-06-21T06:05:54Z
Fix image path in python.md
----
---
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.
---