anchor.diff:    configuration. Cloudera hosts the Gerrit server and a Cloudera employee will
     have to perform this step because SSH access is behind a firewall. The steps
     are as follows:
  -  1. Ensure your public SSH key is in `~gerrit/.ssh/authorized_keys` on gerrit.cloudera.org
  +  1. Ensure your public SSH key is in `~gerrit/.ssh/authorized_keys` on
  +     gerrit.cloudera.org
     2. From behind the firewall, `ssh gerrit@gerrit.cloudera.org` to log in.
     3. Back up the existing replication configuration file by executing
        `cp ~/etc/replication.config ~/etc/replication.config.bak.`date '+%Y%m%d.%H%M%S'``
  -  4. Edit `etc/replication.config` to add a line for the new branch, such as `branch-1.x.y`
  +  4. Edit `etc/replication.config` to add a line for the new branch, such as
  +     `branch-1.x.y`
     5. Send email to the dev lists for Kudu and Impala (dev@kudu.apache.org and
        dev@impala.apache.org) indicating that you are going to restart Gerrit
        (link:https://s.apache.org/2Wj7[example]). It is best to do the restart at
  
positive.code: 
  . As needed, patches can be cherry-picked to the new branch.
  
  == Updating Versions In Master
  
  . Check out the `master` branch and bump the version in `version.txt`.
  
  . Commit and push that change to Gerrit.
  
  . Notify dev@kudu.apache.org that the new branch is available.
  
  
  == 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):
  +
  ----
    ./build-support/build_source_release.py
  ----
  
  . Fix any issues it finds, such as RAT.
  
  . Test the full Java build. This will sign and build everything without
    deploying any artifacts:
  
negative.code: 
  . Build a source tarball against the RC branch.
  
  . Out of the Kudu git workspace, checkout the
    link:https://dist.apache.org/repos/dist/dev/kudu/[dev Subversion (SVN) repository].
    Create a new sub-directory named correspondingly. Copy the artifacts to this
    sub-directory and commit.
  +
  ----
    svn co --depth=immediates https://dist.apache.org/repos/dist/dev/kudu/ kudu-dev-release
    cd kudu-dev-release
    mkdir 1.x.y-RC1
    cp <path_to_kudu_git_workspace>/build/apache-kudu-1.x.y.tar.* 1.x.y-RC1
    svn add 1.x.y-RC1
    svn commit --username=<your_apache_username> -m "Adding Kudu 1.x.y RC1"
  ----
  
  . Create a Maven staging repository for the release candidate Java artifacts.
  