anchor.diff:  === Making a Release Candidate
   
   NOTE: These instructions are for building HBase 1.0.x.
  -For building earlier versions, the process is different.
  +For building earlier versions, e.g. 0.98.x, the process is different.
   See this section under the respective release documentation folders.
   
   .Point Releases
  
positive.code: A good test for the src tarball being 'complete' is to see if you can build new tarballs from this source bundle.
  If the source tarball is good, save it off to a _version directory_, a directory somewhere where you are collecting all of the tarballs you will publish as part of the release candidate.
  For example if you were building an hbase-0.96.0 release candidate, you might call the directory _hbase-0.96.0RC0_.
  Later you will publish this directory as our release candidate up on pass:[http://people.apache.org/~YOU].
  
  . Build the binary tarball.
  +
  
negative.code: Tag before you start the build.
  You can always delete it if the build goes haywire.
  
  . Sign, fingerprint and then 'stage' your release candiate version directory via svnpubsub by committing your directory to link:https://dist.apache.org/repos/dist/dev/hbase/[The 'dev' distribution directory] (See comments on link:https://issues.apache.org/jira/browse/HBASE-10554[HBASE-10554 Please delete old releases from mirroring system] but in essence it is an svn checkout of https://dist.apache.org/repos/dist/dev/hbase -- releases are at https://dist.apache.org/repos/dist/release/hbase). In the _version directory_ run the following commands:
  +
  [source,bourne]
  ----
  