Update doc submodule pointer to latest wiki commit
Copy prerelease Furnace generators into titan-test

titan-test uses com.tinkerpop.furnace.generators, but Furnace has yet
to be released.  Only SNAPSHOT versions are available.  We can't
release Titan with a SNAPSHOT dependency on Furnace.  As a hack, I
copied the source for the generators subpackage into titan-test's
source tree and changed the package name to
com.tinkerpop.furnace.alpha.generators.  The generators subpackage
happens to be self-contained and depends on no other Furnace files.

I commented the Furnace SNAPSHOT dependency in titan-test/pom.xml.

This should all get reverted when Furnace releases and we can depend
on it in releases.
Tweaks to satisfy the release plugin

The release:prepare goal solicits a new version for titan-dist-parent,
but because it only appears through pom inheritance and not through a
module relationship, it appears to do nothing with that new version,
leading to an error in release:prepare's invocation of the verify
phase.  This hack attempts to trick release:prepare into adding
titan-dist-parent as a submodule of the toplevel pom.
Enable release-plugin autoVersionSubmodules
[maven-release-plugin] prepare release 0.4.0
[maven-release-plugin] prepare for next development iteration
Delete old ${titan.version} pom.xml property

The pom.xml property ${titan.version} has been unused for ages since
all uses of it were replaced by ${project.version}.  Having copies of
${project.version} is a DRY hazard -- better just to use
${project.version} unless there is an actual need to allow
differences, as in ${titan.compatible.versions}.  Deleted.
Delete gh-pages profile from titan-site

I used this profile to experiment with the Github maven plugin, but it
proved too destructive in testing to use in actual releases.  It
doesn't appear to offer an easy way to replace a subdirectory with a
new one a la rsync, so its tricky bordering on impractical to use it
to modify subdirectories of gh-pages's javadoc and wikidoc
directories.  All its prospective titan-site functionality has been
subsumed in the gh-pages-update.sh script anyway.
Update gh-pages index.html template
Remove symlinking from gh-pages-update

gh-pages does not support symlinks and returns 404s on them
Update outdated titan-dist/README.md
Document Titan release process RELEASING.md
Make rewrite-tag.sh more robust

This script now reads the current HEAD branch using `git symbolic-ref`
and attempts to return to that HEAD after rewriting the release tag.
Release instructions update
Update doc submodule pointer to latest wiki
Adding Metrics Ganglia and Graphite support

This commit is totally untested.  This commit also javadocs all public
methods in the MetricManager class.
Tested and tweaked Ganglia Metrics reporter

* added new Ganglia Metrics reporter configuration sanity checks
* added option to set GMetric "spoof" option
* commented body of the Graphite Metrics reporter config method until
  its implemented
* javodoc'd Ganglia configuration option constants and added their
  associated default values as constants
Cleanup imports in MetricManager and GraphDBConfig
Rename metrics.ganglia.host to .hostname

Matches storage.hostname.  There's no technical reason they have to
match, I'm just trying to stick to precedent.
Added Metrics Graphite reporter support

I just tested this against a local Graphite instance and successfully
ingested data and exercised the Graphite "prefix" config option, but I
didn't scrutinize the results beyond that.  This Graphite reporter
support should be considered lightly tested.