3 ms·
GitFlow and it's derivatives have very poor handling for continued bug fixes of old released versions. It might be great for a truly continuous model such as Fa
by vidanay 10y ago
GitFlow and it's derivatives have very poor handling for continued bug fixes of old released versions. It might be great for a truly continuous model such as Facebook and Gmail where there is only "one true version", but in a case where there is a current version and three old versions requiring bug fixes, it fails miserably.
- Horba 10y agoI've implemented GitFlow with multiple support versions. We just added a "version" dimension to each of the main branches. 1.1/master 1.1/release 1.1/development 1.2/master 1.2/release 1.2/development When we fix bugs in 1.x, we work off 1.1/development and merge into all later versions. This doesn't fit for a "web" or "continuous delivery" model. It does fit very well for software houses with many customers on 6 monthly upgrade / development cycles.
- joneholland 10y agoI'm not talking about git flow.