anchor.diff:    gradle clean uploadArchives -PmavenUsername="<APACHE-LDAP-USERNAME>" -PmavenPassword="<APACHE-LDAP-PASSWORD>"
   ----
   +
  -Go to the link:https://repository.apache.org/\#stagingRepositories[staging repository]
  -and look for ‘orgapachekudu-####’ in the staging repositories list. You can
  -check the ‘content’ tab at the bottom to make sure you have all of the expected
  -stuff (client, various integrations, etc). Hit the checkbox next to your new
  -staging repo and hit “close”. Enter something similar to “Apache Kudu 1.x.y-RC1”
  -into the description box and confirm. Wait a minute or two and hit refresh, and
  -your staging repo should now have a URL shown in its summary tab (eg
  -`https://repository.apache.org/content/repositories/orgapachekudu-1005`)
  -
  -. Add your PGP key to the KEYS file:
  +Go to the link:https://repository.apache.org/\#stagingRepositories[staging
  +repository] and look for ‘orgapachekudu-####’ in the staging repositories list.
  +You can check the ‘content’ tab at the bottom to make sure you have all of the
  +expected stuff (client, various integrations, etc). Hit the checkbox next to
  +your new staging repo and hit “close”. Enter something similar to “Apache Kudu
  +1.x.y-RC1” into the description box and confirm. Wait a minute or two and hit
  +refresh, and your staging repo should now have a URL shown in its summary tab
  +(eg `https://repository.apache.org/content/repositories/orgapachekudu-1005`)
  +
  +. Create a new folder containing the
  +  link:https://dist.apache.org/repos/dist/release/kudu/[release SVN
  +  repository]. For a release to be made official, it must eventually be put in
  +  this repository. Add your PGP key to the KEYS file:
   +
   ----
   svn co https://dist.apache.org/repos/dist/release/kudu/ kudu-dist-release
  
positive.code: . Always send an email with a different subject to indicate the result. For
    link:http://mail-archives.apache.org/mod_mbox/kudu-dev/201606.mbox/%3CCAGpTDNeJdU%2BoUF4ZJneZt%3DCfFHY-HoqKgORwVuWWUMHq5jBNzA%40mail.gmail.com%3E[example].
  
  . After the vote passes, send an email to dev@kudu.apache.org
    indicating the result.
  
  == Release
  
  . Create a new folder in https://dist.apache.org/repos/dist/release/kudu/,
    copy the files from the release candidate’s folder in dist/dev/kudu/, then commit.
  +
  ----
    cd kudu-dist-release
    mkdir 1.x.y
    cp <path_to_rc_artifacts>/* 1.x.y
    svn add 1.x.y
    svn commit -m "Adding files for Kudu 1.x.y"
  ----
  
  . In the Kudu git repo, create a signed tag from the RC’s tag, and push it to the
  Apache Git repository:
  +
  ----
    git tag -s 1.x.y -m 'Release Apache Kudu 1.x.y' 1.x.y-RC1
  
negative.code: ----
  
  . Push the branch to public remotes https://github.com/cloudera/kudu.git and
    https://gitbox.apache.org/repos/asf/kudu.git. The following example assumes
    they are called `cloudera` and `apache`.
  +
  ----
    git push cloudera branch-1.x.y
  