superset-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [incubator-superset] branch master updated: [docs] minor file name and format fix for the setup document (#4844)
Date Thu, 19 Apr 2018 18:34:26 GMT
This is an automated email from the ASF dual-hosted git repository.

maximebeauchemin pushed a commit to branch master
in repository

The following commit(s) were added to refs/heads/master by this push:
     new 860a4d9  [docs] minor file name and format fix for the setup document (#4844)
860a4d9 is described below

commit 860a4d91238ef36447aa98f9407bfd253bc4750a
Author: Kengo Seki <>
AuthorDate: Fri Apr 20 03:34:23 2018 +0900

    [docs] minor file name and format fix for the setup document (#4844)
--- | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/ b/
index 10d82d1..519644a 100644
--- a/
+++ b/
@@ -106,7 +106,7 @@ Finally, to make changes to the rst files and build the docs using Sphinx,
 you'll need to install a handful of dependencies from the repo you cloned:
     cd incubator-superset
-    pip install -r docs/requirements-docs.txt
+    pip install -r docs/requirements.txt
 To get the feel for how to edit and build the docs, let's edit a file, build
 the docs and see our changes in action. First, you'll want to
@@ -417,8 +417,7 @@
   Every once in a while we want to compile the documentation and publish it.
   Here's how to do it.
-  .. code::
     # install doc dependencies
     pip install -r docs/requirements.txt
@@ -441,6 +440,7 @@
     git add .
     git commit -a -m "New doc version"
     git push origin master
 ## Publishing a Pypi release
@@ -453,8 +453,7 @@
   Following a set of cherries being picked, a release can be pushed to
   Pypi as follows:
-  .. code::
     # branching off of master
     git checkout -b 0.25
@@ -489,6 +488,7 @@
     # this will overwrite the with only the version range
     # so you'll want to copy paste that on top of the previous
     # open a PR against `master`
   In the future we'll start publishing release candidates for minor releases
   only, but typically not for micro release.

To stop receiving notification emails like this one, please contact

View raw message