Yep, that's how I do it too. I've got to say that using Capistrano's default deploy.rb seems over-designed for my tastes. I mean, if I'm deploying code from a version control system, why would I want to have a second version control system to track releases?
For me, I want to have a second version control system to track releases. For my personal projects, I deploy as soon as I have something interesting, which might be once a week or might be five times in an hour, and I deploy straight from the HEAD of master. If I deploy something prematurely, a symlink repoint and a restart can be done via Cap, or manually, or whatever.
Making Git also control my deploys would mean either tagging release commits or rebasing onto a production branch, which both (for me, at least) impede releasing as often as I can.
I've got the 'tag, push, rebase, restart' and 'oshit, rollback, restart' as ordinary rake tasks, so it's not like there's much cognitive load there. I've bothered with cap in the past if I've been pushing to more than one server, but it's not that much more effort to just do "ssh in a loop" and avoid a dependency.
