workflow - Is there a conventional way to support more than one release in git? -


Whether a git workflow is designed to keep software from many GIT branches (for example, release.1.1 Master long time ago, and release.1.2 more recently than guru). There are great documents in the feature branch workflow, gifflow workflow, and forking workflow but I have not got information about managing more than one release.

Managing multiple releases will require the use of hotfixes and facilities for one or more Release Branches will be used to maintain all the changes for future releases, a Master branch will be used, The master's closest release can get some features and hotfix, the most release release will receive at least the update, and the Chutuli release from the Guru is the first initiative It will reach the end, life will be.

I am thinking that something like this will appear

  Master ------- + ---------- + - --- ----- + ---------- + ------ + ----------- + ----------- --- ------ \ \ \ / \ / hotfix- + feature- + \ \ hotfix feature \ release_1.2 ------- + --------------- --- + --------------- \ hotfix release_1.1 ------------------ + --- ---- --------------- End-of-life  

The following is modified to look like a ghit flow, but a 'release_1.1 'Branch.

Release_1.1 --------- + --------- + --- | \ / || Hotfix 3 | Tags 1.0 Tags 1.0.1 1.1 1.1 Tags 1.1.1 Tags 1.2 1.2.1 1.2 | | | | | | Master + ----------- + ------------- + -------- + ------------- + -------- + ------------------ | / / / / / | //// Hotfix 1 / Hotfix 2 / Hotfix Release 3 | \ + - + - + + + + + - + \ | \ / \ \ \ \ \ Evolution + - + -------- + --- + ------- + - + -------- + --- --- - ------ + ---------- + ------ \ / \ / FeatureA- + FeatureB-+

< Div class = "post-text" itemprop = "text">

You can not merge the old release based on the current master hotfix branch - this is guru In the old release too, you will have to select all the code as the basis of your hotfix branch with the common ancestor of your code, usually the point where the oldest amendment still master . From there, for each release, (1) the hotfix branch is merged into the release bracket, and then (2) merge the point where the next release was replaced by the master to the hotfix branch. And resolves conflicts. Finally, merge the hotfix branch back into master .

You may want to keep an eye on you.


Comments

Popular posts from this blog

import - Python ImportError: No module named wmi -

Editing Python Class in Shell and SQLAlchemy -

c# - MySQL Parameterized Select Query joining tables issue -