Revert "travis?"

This reverts commit 10e9b0572a8bad2e9b0814de370ce9b53a754c43.
Revert "Travis!!"

This reverts commit ef2800c49bfe513a7ce0b759a3b015b87d42282e.
Revert "Travis!"

This reverts commit 1a864f3ce0a665f2057144e068f2b54b43d49271.
Revert "remove Cartridge.lock, have Travis grab it from the workspace"

This reverts commit 0150725192c8bc1b2cdf8d4aefa196a22b816e2a.
use bleeding-edge for everything

The hope is to find a workflow that keeps us from straying behind in
separate components, while also locking them down individually for CI
and release cutting, etc. This accomplishes the second and "eventually"
accomplishes the first, as using bleeding-edge means we're constantly
bumping automatically during development.