Everyone a great god, I meet a problem now, the younger brother is a testing engineer, leadership put forward how to control the parallel version of some of the questions, as follows
1. Super fast version iteration, is almost a day on a version
2. In addition to the regular version, also because of urgent needs emergency BUG, leading to release every day
3. Because the fast iterative problem, which leads to the development of the communication not smooth forgotten baseline, forget between parallel versions merging, lead to online leak code, code rolled back, the problem of each frequency
So I hope you can help me to analyse the problem and the solution, the existing two ideas
1. Whether is there any way to control the parallel between versions, or emergency version automatically check pulled baseline has been consolidated, otherwise refused to submit code automatically
2. If for code review, when should undertake, what are the critical standards, all parties need to provide what, after finally what results can submit code, then go online

CodePudding user response:

Each online version to play tag, the new version for a new branch

Need and bug management together