anchor.diff:  . When ready, create a new lightweight tag and push it to the Apache Git repository.
   +
   ----
  -  git tag 1.x.0-RC1
  -  git push apache 1.x.0-RC1
  +  git tag 1.x.y-RC1
  +  git push apache 1.x.y-RC1
   ----
   
   . Build a source tarball against the RC branch.
  
positive.code:   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
    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`
    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
       some time of day when you don't expect many people to be using the system,
       since Gerrit can take a few minutes to restart.
  
  . As needed, patches can be cherry-picked to the new branch.
  
  
negative.code: ----
  
  . Push the branch to public remotes https://github.com/cloudera/kudu.git and
  https://git-wip-us.apache.org/repos/asf/kudu.git. The following example
  assumes they are called `cloudera` and `apache`.
  +
  ----
  