We follow git flow, see https://nvie.com/posts/a-successful-git-branching-model/
Lets imagine the following situation:
We have a current version 2.0.8 on our prod environment. After a while, several bugs appearing that need to be fixed (no hotfixes, because they are not critical but more urgent than new features). But in the meanwhile the development on dev branch is ongoing and many new features and other bugfixes are already on current dev branch. However, management decides that the next version is just about fixing the recently discovered bugs, but without any current new features.
Where does the bugfix take place in this case?
For me it cannot be placed on a new branch from current dev because this also would involve the new features we don't want right now ...
Intuitively I would say, branching from the current deployed master tag (2.0.8), applying the fixes and merge back to master and tag it with a new version (2.0.9). Then merge the changes also to the current develop (hopefully nobody touched the code in the meanwhile) ... but I wonder why there is no such case shown in the git flow graph? What do I miss here?