I don't think it's a good idea to include wiki content in a release.

What I've seen other projects use their wiki space for effectively is:

* Contributor guides
* Tutorials
* Design documents/proposals

I think the reason that some wikis experience content rot is they
never build a big enough user base and they're outside of the release
process so there's no forcing function to review that content is

For communities that are still relatively small, you can tag specific
pages as things that should/need to be periodically reviewed and could
assign JIRAs or some other notification mechanism to kick off a


Joey Echeverria
Chief Architect
Cloudera Government Solutions
On Wed, Apr 23, 2014 at 11:19 AM, Bill Havanki

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