David E. Wheeler

I see, the problem is that you can have two versions in production at once. So if you add a chance to your `v2` branch and release, and then add...

It would most likely end up requiring a new plan format to support multiple parents.

The reason it uses a git history/BitCoin blockchain-like approach is to _guarantee_ that things are always deployed in the correct order. This has saved us from fucking up production deployments...

I've been thinking about this off and on for the last few weeks. I think that, if we want to get something done in time for v1.0.0. it wouldn't be...

I've now implemented the `upgrade` command and closed #87.

> To survive this, we've developed a helper tool for sqitch that identifies discrepancies between a sqitch filesystem and a target database. It recognizes changes that have been inserted, deleted...

> insert - add a new or reworked change between existing tags. I realize some teams may not want to use this in their respective workflows, so maybe have it...

> Much of the errors could also be avoided if we continue with the git metaphor and add "staging" support. > - Changes could be collected in a staging area...

> Completely agreed. My current client is hiring plenty of devs and not all of them take the time to read the documentation or, if they do, they don't always...

Okay, with [these commits](https://github.com/theory/sqitch/compare/fd0c39d...bb8f8cc5), I've added support for logging the deploy script hash along with each change. With that in place, I propose a first pass at reconciling differences between...