+Paddy Foran +Robert Norris
Using `git` as source control and following a strategy similar to Atlassian's "simple git workflow" I don't see committing broken code to be a problem in a DVCS. (http://blogs.atlassian.com/2014/01/simple-git-workflow-simple/
My current workflow requires rebasing my WIP branches on top of the release branch before merging to release. (So all merges to release are fast-forward.)
Since my WIP branch is going to be rebased anyways that automatically rules out sharing my WIP branch with colleagues.
In addition I can squash the "broken" commit w/ the next morning's commit that would fix it so that such a broken commit doesn't end up on the release branch :)