anchor.diff:  
   
   == Preparing A Release Candidate
  +
  +. Before building a release candidate, make sure you have followed the
  +Apache committer guide for setting up your GPG keys
  +(link:https://www.apache.org/dev/new-committers-guide.html#set-up-security-and-pgp-keys[here]).
   
   . When close to building a release candidate, try building a source tarball
   (on a supported platform):
  
positive.code: 
  . About another 24 hours later, delete the previous minor version in the branch
    you released from, from SVN. For example, if you released 1.2.1, delete `1.2.0`.
  
  . Update the version number on the branch you released from back to a SNAPSHOT
    for the next patch release, such as `1.6.1-SNAPSHOT` after the `1.6.0` release.
  
negative.code:   and click 'Release'.
  
  . Generate the version-specific documentation from that branch following these
    link:https://github.com/apache/kudu/#updating-the-kudu-web-site-documentation[instructions].
  
  . Replace the `apidocs` and `docs` folders in the `gh-pages` branch with the new documentation.
  
  