I've done the big projects, with years (well months) worth of work bundled into a huge patch in zilla and based on that experience, I'm all for a workflow that encourages publishing changes in a more digestible manner, where they can be reviewed in a timely manner, and tweaks can be more easily reviewed separate from (but in the context of) the previous patch.
And I'm not saying that devs who go purely through Zilla are the ones doing it wrong! On a project level, we, Dreamwidth, have not made it easy to do it any other way. And we need to change that, whether it's Mercurial or Git (or whatever) we use as a repo.
no subject
And I'm not saying that devs who go purely through Zilla are the ones doing it wrong! On a project level, we, Dreamwidth, have not made it easy to do it any other way. And we need to change that, whether it's Mercurial or Git (or whatever) we use as a repo.