anchor.diff:    copy the `apidocs`, `cpp-client-api`, and `docs` folders there, copy an `index.md` file from one
     of the other releases and modify it accordingly.
   
  -. Commit all these changes.
  -
  -. Create a new review for all those new and updated files in `gh-pages`.
  +. Submit these changes to the `gh-pages` Gerrit branch and get them reviewed.
   
   . Once the review is finished and the commit is pushed, update the website following
     these link:https://github.com/apache/kudu/#deploying-changes-to-the-apache-kudu-web-site[instructions].
   
   . About 24 hours after the first step was completed, send an email to
  -  user@kudu.apache.org, dev@kudu.apache.org, and announce@apache.org
  -  to announce the release. The email should be similar to
  +  user@kudu.apache.org, dev@kudu.apache.org, and announce@apache.org to
  +  announce the release. The email should be similar to
     link:https://s.apache.org/pduz[this].
   
  -. About another 24 hours later, delete the previous minor version in the branch
  -  you released from, from SVN. For example, if you released 1.2.1, delete `1.2.0`.
  -  Also delete any release candidates from the dev SVN.
  +. About another 24 hours later, clean up the SVN. If releasing a new minor
  +  version, delete the oldest minor version branch in the release repo (e.g. if
  +  `1.7.1`, `1.8.0`, and `1.9.0` exist and you just released `1.10.0`, delete
  +  `1.7.1`). If releasing a maintenance version, delete the previous maintenance
  +  branch (e.g. if you released `1.2.1`, delete `1.2.0`). Also delete any
  +  release candidates from the dev SVN.
   
   . Update the version number on the branch you released from back to a SNAPSHOT
     for the next patch release, such as `1.6.1-SNAPSHOT` after the `1.6.0` 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: 
  . Build a source tarball against the RC branch.
  
  . Create a new folder containing the
    link:https://dist.apache.org/repos/dist/dev/kudu/[dev Subversion (SVN)
    repository]. Copy the artifacts to this folder and commit.
  +
  ----
    svn co --depth=immediates https://dist.apache.org/repos/dist/dev/kudu/ kudu-dev-release
  