version control - Separated branch for each bugfix vs graft from dev branch -


I have an application with 3 environments - Dev, Forum and Production.

Bug fixes and features typically have 2/3 commitments.

Currently I use the Mercurial Project for myself, but I can not decide how to go, it is best to use named branches, but I do not know that 1/2 / This is right for 3. I think grafts also look promising.

So I have a question that if I need to be able to separate the different changes, then what do I need?

easy in the future (if necessary) find out the part of the history of the repo, which has been completed. WIP related to the job (only That's because the name of the unique branch in each branch is permanent metadata, and The common name is shared with other names in the form of shared parents / branch / bookmark-driven / history and other changes in history).

Single defect of intensive use of named branches After some time, HG branches I like to use nominated branches because it gives a recoverable history and more polluted log of change: Repeat changes with coherent changes. The article instead I see that merge for each integration of a work repository identifies all merge-target


Comments

Popular posts from this blog

java - org.apache.http.ProtocolException: Target host is not specified -

java - Gradle dependencies: compile project by relative path -

ruby on rails - Object doesn't support #inspect when used with .include -