anchor.diff:  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 a 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 http://people.apache.org/~YOU. 
  +Later you will publish this directory as our release candidate up on http://people.apache.org/~YOU.
   
   . Build the binary tarball.
   +
  
positive.code: ====
  
  Similarly, for 3.0, you would just replace the profile value.
  Note that Hadoop-3.0.0-SNAPSHOT does not currently have a deployed maven artificat - you will need to build and install your own in your local maven repository if you want to run against this profile. 
  
  In earilier versions of Apache HBase, you can build against older versions of Apache Hadoop, notably, Hadoop 0.22.x and 0.23.x.
  If you are running, for example HBase-0.94 and wanted to build against Hadoop 0.23.x, you would run with:
  
negative.code: .Excluding Non-Public Interfaces from API Documentation
  [NOTE]
  ====
  Only interfaces classified `@InterfaceAudience.Public` should be included in API documentation (Javadoc). Committers must add new package excludes `ExcludePackageNames` section of the _pom.xml_ for new packages which do not contain public classes.
  ====
  
  .@InterfaceStability
  