This is an automated email from the ASF dual-hosted git repository.
jhyde pushed a commit to branch site
in repository https://gitbox.apache.org/repos/asf/calcite.git
The following commit(s) were added to refs/heads/site by this push:
new 2850379 Update instructions for publishing site; we previously used
subversion, now we use git
2850379 is described below
commit 2850379f6d0fbb3c43ce21fdff91da7582510db0
Author: Julian Hyde <[email protected]>
AuthorDate: Wed Mar 27 16:31:46 2019 -0700
Update instructions for publishing site; we previously used subversion, now
we use git
---
site/README.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/site/README.md b/site/README.md
index 831f220..2c02b54 100644
--- a/site/README.md
+++ b/site/README.md
@@ -31,7 +31,7 @@ You can build the site manually using your environment or use
the docker compose
Site generation currently works best with ruby-2.5.1.
1. `cd site`
-2. `svn co https://svn.apache.org/repos/asf/calcite/site target`
+2. `git clone https://gitbox.apache.org/repos/asf/calcite-site.git target`
3. `sudo apt-get install rubygems ruby2.5-dev zlib1g-dev` (linux)
`Use RubyInstaller to install rubygems as recommended at
https://www.ruby-lang.org/en/downloads/` (Windows)
4. `sudo gem install bundler`
@@ -125,7 +125,7 @@ sync with "master". Immediately after a release, the
release manager
will publish the site, including all of the features that have just
been released. When making an edit to the site, a Calcite committer
must commit the change to the git "master" branch (as well as
-subversion, to publish the site, of course). If the edit is to appear
+git, to publish the site, of course). If the edit is to appear
on the site immediately, the committer should then cherry-pick the
change into the "site" branch. If there have been no feature-related
changes on the site since the release, then "site" should be a
