docs: better wording in release notes
docs: added explicit TOC link to license section
test: upgrade to a version of mongodb that exists
test: mysql setups fails more loudly
test: mysql setup on Ubuntu 13.10 requires setting user explicitly
test: user may not have permission on default socket/pid files
config: strip surrounding whitespace from env vars
test: 0.8 docker CI needs longer timeout
test: vm may take a while to boot in virtualized environments
instrumentation: nerf logging level
instrumentation: hapi (WIP)
instrumentation: remove confusing Express comment
test: hapi 1.20.0 requires node > 0.9

Maybe it's worth adding integration tests that exercise hapi 0.16.0,
which supported 0.8, but this is the fastest way to do it without
requiring any brittle tap workarounds.
instrumentation: DRY up wrapping

Everything depends on Hapi.Server.prototype, so we might as well save
some function calls if it's not available.
urltils: put parameter copying in one place

awinterman pointed out on twitter that relying on a Node core private
API call (util._extend()) was probably unsafe and a bad example for the
children. Not only that, it was duplicated all over the place, not
tested, and allocated more objects than necessary. Now there's one
function that will handle this everywhere, dedicated unit tests, and a
simpler overall implementation.
instrumentation: gotta wrap 'em all
instrumentation: handle hapi's full complexity

Hapi's router is very flexible, and there's no real way to ensure that
all route handlers are instrumented as expected without treating the
router, in part, as a black box. Hapi's great for performance
observability, but not so great for ad hoc instrumentation.
test: rewrote hapi tests to be more deterministic
instrumentation: hapi 2 is a little different
instrumentation: rendering may out of transaction