Fix revisions to tags for release
Fix folsom dependency
Don't crash the cache when a stat mod crashes

Since calls to calculate stats are spawn_linked to ensure
that the calculating processes exits if the cache exits, the cache
will crash if a spawned process exits. This is bad. This change
traps_exits on spawned processes and enforms awaiting callers of
the error, without crashing the cache or effecting other registered
mods.
Merge pull request #210 from basho/rdb-stat-crash

Don't crash the cache when a stat mod crashes
Fix tag on riak_sysmon to be 1.1.2
remove duplicated include

Signed-off-by: Peter Lemenkov <lemenkov@gmail.com>
Guard all unguarded eunit includes

Signed-off-by: Peter Lemenkov <lemenkov@gmail.com>
global:safe_whereis_name/1 has been removed
Register stat mods with the riak_core app

When the stat cache crashes, we must re-register stat mods with
the cache so that it works when re-started.

Delete stats before register

This is to ensure that a restarted riak_core_stat will not
leave any orphaned folsom stats. Folsom needs some work to handle
crashing owners better. Some table in folsom are owned
by the creating process, and some by folsom. If riak_core_stat
crashes some folsom can be left inconsistent. This cleans up
at start time.
Merge branch 'rdb-stats-re-register' into 1.2
Merge branch '1.2'
Make the ring manager responsible for loading the ring

Change riak_core_ring_manager and riak_core_app so that the ring manager
is responsible for loading the ring file from the disk rather than starting
with an initially empty ring and then relying upon the riak_core app to
later load the ring. This avoids a race condition with the ring manager
writing the empty ring to the disk before the riak_core app loads the
prior ring.

Note: Riak previously relied upon starting with a fresh ring in order to
ensure secondary vnodes were started in case any had fallback data that
needed to be handed off. The act of starting secondaries has long since
been moved to the riak_core_vnode_manager that periodically starts up
secondary vnodes over time, therefore there is no longer any need to
start with a fresh ring. This commit will therefore always load a saved
ring when the ring_manager starts, rather than starting with a fresh ring.
Fix capability system race condition

Prevent the node from crashing when the capability system attempts to
negotiate capabilities before the node has registered any capabilities.
Merge pull request #214 from basho/jdb-ring-manager-load

Fix race during start-up that could overwrite existing ring file.
Fix issue #166.

Merge branch '1.2'
Merge pull request #216 from basho/jdb-capability-crash
Change ticks from timer to more efficient erlang:send_after
restructure supervision tree so that folsom is an included app

All stat mods depend on folsom, yet they are not linked to it.
This change brings folsom under supervision of a core stat sup,
which also supervises the riak stat subsystem. Now when folsom exits
everyone gets to restart clean and recover.

riak_core_sup
    |
riak_core_stat_sup (rest_for_one)
    \
       - folsom_sup
       - riak_core_stats_sup (one_for_one)
        \
          - riak_*_stat
          - riak_stat_cache

riak_core_stats_sup will start and supervise gen_server stat mods at
registration time, and will re-start them should the sup crash.
Fix spurious "Forcing update of stalled ring"

Changed the force update logic in riak_core_claimant to not perform
a forced update if we have pending staged joins and no auto-joining
nodes. Forcing a ring update because of staged joins will not actually
change the ring, because staged joins will not transition until
committed. This was a false positive detection of a stalled ring.
Merge pull request #218 from basho/jdb-ring-updates-when-joining