Mike Percy has posted comments on this change. ( http://gerrit.cloudera.org:8080/8800 )
Change subject: docs: Add scripts to automate web site update for releases ...................................................................... Patch Set 1: (1 comment) http://gerrit.cloudera.org:8080/#/c/8800/1/docs/support/scripts/prepare_release_docs.sh File docs/support/scripts/prepare_release_docs.sh: http://gerrit.cloudera.org:8080/#/c/8800/1/docs/support/scripts/prepare_release_docs.sh@68 PS1, Line 68: git commit -m "Updating web site for Kudu $VERSION release" > Should this change gerrit change be in the gh-pages branch? So you can run It assumes you already did that. If we want it to do that we could, with the caveat that we would also need to set up the gerrit git trigger, but I'm not sure the best way to do that. Maybe we could find the current gerrit trigger and replicate it in the checked out version of the gh-pages tree? -- To view, visit http://gerrit.cloudera.org:8080/8800 To unsubscribe, visit http://gerrit.cloudera.org:8080/settings Gerrit-Project: kudu Gerrit-Branch: master Gerrit-MessageType: comment Gerrit-Change-Id: If55437e0561f0bf8e5e0ec0ae6e5bfca0311fb7d Gerrit-Change-Number: 8800 Gerrit-PatchSet: 1 Gerrit-Owner: Mike Percy <mpe...@apache.org> Gerrit-Reviewer: Dan Burkert <danburk...@apache.org> Gerrit-Reviewer: Grant Henke <granthe...@apache.org> Gerrit-Reviewer: Kudu Jenkins Gerrit-Reviewer: Mike Percy <mpe...@apache.org> Gerrit-Comment-Date: Tue, 10 Apr 2018 20:58:17 +0000 Gerrit-HasComments: Yes
