Attila Bukor 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:

(2 comments)

Mike, could you also add this to the RELEASING docs after the make_site.sh 
paragraph?

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"
> It assumes you already did that. If we want it to do that we could, with th
I think it would be a good idea to document these kind of stuff. It doesn't 
seem straight-forward. Also, the docs could potentially mention that git 
worktree can be used to check out the gh-pages branch instead of multiple 
clones of the repo (Todd mentioned it the other day and it's a game changer)


http://gerrit.cloudera.org:8080/#/c/8800/1/docs/support/scripts/release_index.md.template
File docs/support/scripts/release_index.md.template:

http://gerrit.cloudera.org:8080/#/c/8800/1/docs/support/scripts/release_index.md.template@37
PS1, Line 37:   
[MD5](https://www.apache.org/dist/kudu/%VERSION%/apache-kudu-%VERSION%.tar.gz.md5),
MD5 should be removed too



--
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 <[email protected]>
Gerrit-Reviewer: Attila Bukor <[email protected]>
Gerrit-Reviewer: Dan Burkert <[email protected]>
Gerrit-Reviewer: Grant Henke <[email protected]>
Gerrit-Reviewer: Kudu Jenkins (120)
Gerrit-Reviewer: Mike Percy <[email protected]>
Gerrit-Comment-Date: Wed, 24 Oct 2018 21:09:27 +0000
Gerrit-HasComments: Yes

Reply via email to