Git flow assigns version numbers based on tags. Therefore, it is impossible to maintain multiple active versions.
For example:
HashData released version 1.0, followed by version 1.1. At this time, I found a bug in 1.0, which has been fixed in 1.1. Users of 1.0 need a fix, but don't want to upgrade to version 1.1 (major version upgrades require additional fees). What should I do if I need to release a 1.0.1 version?
The answer is that git flow can't do it. You need to create a new 1.0.1 branch from the 1.0 tag, which is not within the rules of git flow.
So git flow is more suitable for projects with only one active release, such as websites. Traditional software products need to maintain multiple active releases at the same time. So not applicable.
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
Git flow assigns version numbers based on tags. Therefore, it is impossible to maintain multiple active versions.
For example:
HashData released version 1.0, followed by version 1.1.
At this time, I found a bug in 1.0, which has been fixed in 1.1. Users of 1.0 need a fix, but don't want to upgrade to version 1.1 (major version upgrades require additional fees). What should I do if I need to release a 1.0.1 version?
The answer is that git flow can't do it.
You need to create a new 1.0.1 branch from the 1.0 tag, which is not within the rules of git flow.
So git flow is more suitable for projects with only one active release, such as websites. Traditional software products need to maintain multiple active releases at the same time. So not applicable.