anchor.diff:  
   . Close the Maven staging repository (or repositories).
   +
  -The Maven staging repositories used for the Java and the binary test JAR
  -artifacts must be closed in order to be accessible to people testing the RC.
  -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(s) 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 each closed staging repo should now have a URL shown in its
  -summary tab, for example
  -`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
  -cd kudu-dist-release
  -(gpg --list-sigs <your-email-address> && gpg --armor --export <your-email-address>) >> KEYS
  -svn commit -m "Adding my key to the KEYS file"
  -----
  +Go to the link:https://repository.apache.org/[repository manager] and log
  +into the repository server using your Apache credentials. Make sure to enable
  +Adobe Flash in your browser for this Web site. Now, go 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
  +(e.g. `https://repository.apache.org/content/repositories/orgapachekudu-1005`)
   
   == Initiating a Vote for an RC
   
  -. Send an email to dev@kudu.apache.org to start the RC process, using
  -  this
  +. Send an email to dev@kudu.apache.org to start the RC process, using this
     link:http://mail-archives.apache.org/mod_mbox/kudu-dev/201606.mbox/%3CCAGpTDNduoQM0ktuZc1eW1XeXCcXhvPGftJ%3DLRB8Er5c2dZptvw%40mail.gmail.com%3E[example]
     as a template.
   
  
positive.code:   need to build on an old version of macOS).
  +
  ----
    # Build a binary JAR for the local operating system. The resulting JAR
    # is output into the build/mini-cluster directory.
    ./build-support/mini-cluster/build_mini_cluster_binaries.sh
    # Sign and publish all matching kudu-binary artifacts from the
    # build/mini-cluster directory to the Maven staging repository that hosts
    # the Java artifacts of the Apache Kudu project (see above).
    ./build-support/mini-cluster/publish_mini_cluster_binaries.sh -a=deploy -u='<APACHE-LDAP-USERNAME>' -p='<APACHE-LDAP-PASSWORD>'
  ----
  +
  NOTE: If the binary test JAR artifacts are deployed by the same person and from the
  
negative.code:   # Run a gpg-agent if you don't normally
    gpg-agent --daemon
    cd java
    # Turn off bash history: this is to avoid exposing the credentials
    # via .bash_history file.
    set +o history
    ./gradlew clean uploadArchives \
        -Psigning.gnupg.keyName=<8-character-pgp-key-id> \
        -PmavenUsername='<APACHE-LDAP-USERNAME>' \
        -PmavenPassword='<APACHE-LDAP-PASSWORD>'
    # Turn on bash history.
    set -o history
  ----
  
  . Build and deploy new binary test JARs for the RC on macOS and Linux. Build
  