Hm.. so previously we release the trunk docs with the 0.98 releases?  this
seems strange.  I would think 0.98 docs would be generated from the 0.98
release branch's branch.

It seems reasonable if in our post-git releases we have the source for the
docs in the source tarballs but not the build docs.  The built docs
however, are in the ready-to-use release tarballs and correspond to the
release.  Is this the case now?

Doing this becomes more important because the docs will likely change due
to deployment changes with potentially different rules of thumb etc for
0.98->1.0 vs what will be 2.0 releases.

On Tue, Jul 29, 2014 at 5:23 PM, Andrew Purtell <[EMAIL PROTECTED]> wrote:
// Jonathan Hsieh (shay)
// HBase Tech Lead, Software Engineer, Cloudera
// [EMAIL PROTECTED] // @jmhsieh

NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB