Relevant article: http://endoflineblog.com/gitflow-considered-harmful http://endoflineblog.com/gitflow-considered-harmful In particular, this rings true to eve

Relevant article: http://endoflineblog.com/gitflow-considered-harmful http://endoflineblog.com/gitflow-considered-harmful In particular, this rings true to every complex source control process I've used that isn't actually enforced with software: You could of course say that all of these mistakes are the result of human error, and if the same people just read the documentation and learned from their experiences, everything would be fine. But I have seen these mistakes being made so many times, by otherwise competent developers, that I don't buy this argument. There's a saying I love: "If one person tells you you have a tail, ignore them; if a hundred people tell you that, look behind you". If these mistakes happen over and over again (and I can confirm based on my experience that they do), made by different people in different circumstances, then there's no rational alternative to admitting there has to be something fundamentally flawed about the method being used.