Git flow: best practice for working with small releases

A Git stream uses a specific branch ( master

) for stable releases. Each release is marked with a version number. The git flow diagram further uses the release branches

forked from develop

to prepare the release. However, it appears that these release branches are removed when the release is complete (after the content has been merged back into both masters and developed).

Hotfix

there are branches for solving problems in the release of products, and they are branched out and combined into masters. But, apparently, this is mainly done to prepare a new version of the minor release.

However, how do I resolve minor fixes that don't require a new version? Imagine that I want to collect some small fixes until I release a new small version. Wouldn't it be useful to keep a release for this branch? Or is there another / better solution?

+3
git versioning release git-flow


source to share


No one has answered this question yet

See similar questions:

1
GIT Flow and support for parallel software versions

or similar:

1817
What's the best (and safest) way to merge a Git branch into master?
879
Git workflow and rebase vs merge questions
878
API versioning guidelines?
854
Git for Beginners: The Ultimate Practical Guide
791
Git merge master into feature branch
615
Why is git doing fast merge by default?
402
Merge all changes from another branch into one commit
350
What Git branching models work for you?
76
After git-flow, how should you handle a patch from an earlier version?
53
Git - stream and master with multiple parallel branching branches



All Articles
Loading...
X
Show
Funny
Dev
Pics