Is introduced: in actual project, a group currently has 10 developers, maintenance and development of more simple system at the same time, there has been a v1 version has been launched, the v2 version is testing environment test, v3 version in the development, is the next version to test content, then found online version v1 a system bug, it began to need to specify a certain development stop live now in hand (v3) are likely to do to cut back to release v1 fix bugs, here's the thing: in a period of time is always found in the operation of some people to stir up the branch, the v2 v3 or something close to the v1, lead to test content not to enter the online version, now you have asked to do code review the merger, but the effect is not very ideal, there is a miss, want to consult everybody have what better way?

CodePudding user response:

Git is a management tool, I think you should to view the problem from the perspective of software development methods, looking for solutions,
Personally, I recommend the XP approach, its core values: communication, simple, feedback, and courage,