5 ms·
I've got strong feelings about git-flow, but I think the main thing all these "generic flow" solutions are missing is: what are your project requirements? Some
by viraptor 6y ago
I've got strong feelings about git-flow, but I think the main thing all these "generic flow" solutions are missing is: what are your project requirements?
Some projects need release branches, some projects use continuous deployment, some projects need manual QA, etc. There is no solution that will work for everyone, so unless your flow description starts with assumptions and matching requirements, it's wrong. (for some people reading about it)
- tempodox 6y agoThis one is an ad for a payed service, so one can't expect a broad take on the subject. The usual “caveat emptor” applies.
- viraptor 6y agoI slightly disagree. It doesn't cost anything to prefix: "There are many ways to approach it, which will differ depending on your needs. Here's a solution which we believe will work for most, so we want to name it and make it simple for you to apply." It doesn't take anything away from the rest of the content.