anchor.diff:    # Run a gpg-agent if you don't normally
     gpg-agent --daemon
     cd java
  -  gradle clean uploadArchives -PmavenUsername='<APACHE-LDAP-USERNAME>' -PmavenPassword='<APACHE-LDAP-PASSWORD>'
  +  # 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
  
positive.code: 
  == Release
  
  . Create a new folder in the release repository for the new release and copy
    the files from the dev repository.
  +
  ----
    cd kudu-dist-release
    mkdir 1.x.y
    cp <path_to_kudu-dev-release>/1.x.y-RC1/* 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
    git push apache 1.x.y
  ----
  
  . Release the staged Java artifacts. Select the release candidate staging
    repository in link:https://repository.apache.org/#stagingRepositories[Nexus],
    and click 'Release'. You should shortly be able to see the artifacts in
    link:https://search.maven.org/search?q=g:org.apache.kudu[Maven Central].
  
  . Release the Python artifacts. You will need to setup an account on link:https://PyPi.org[PyPi.org]
    and ask to be added to the kudu-python PyPi project if you have not done this before.
  +
  ----
  # Prepare and sign the python source distribution.
  cd python
  rm -rf dist/*
  python setup.py sdist
  gpg --detach-sign -a dist/kudu-python-1.x.y.tar.gz
  # Upload the distribution to PyPi using twine.
  pip install twine
  twine upload dist/*
  ----
  Note: You can upload to the test PyPi by adding
  `--repository-url https://test.pypi.org/legacy/` to the twine command.
  
negative.code: the link:https://www.apache.org/legal/resolved.html[3rd-party license policy],
  making sure the release doesn't include anything from the
  link:https://www.apache.org/legal/resolved.html#category-x[Category X].
  The command-line snippets in this document are for `bash` (Bourne-again shell).
  To edit or update this document, edit `RELEASING.adoc` in `master`.
  
  == Stating Intent to Release
  