GIT Library Management specification

(1) The newly created branch branch is named with DEV_YYYYMMDD, such as dev_20150804.
(2) The new tag is divided into development dev, return reg, fix hot three kinds, naming methods such as: dev_20150804_01
(3) test process can be handed over to QA for testing, hit dev tag.
(4) When entering the regression phase, merge the Dev branch into the master branch and play the Reg tag.
(5) When the production of serious bugs need to be hotfix, first from the production of Reg tag to pull a branch, named HOT_YYYYMMDD.

Add:

(1) When the project or ECR begins, the subsystem creates a development branch based on the planned on-line date, dev_20150804. (Development branch based on rel_20150802 Tag of the line)

(2) After development handover test, play Tag,tag rule on Development Branch dev_20150804_01 (02, 03 sequence Increase)

(3) After the test is stable, the test sends the notification into the regression test. Development merges the latest content into the master branch, and the tag rule is modified to reg_20150804_01
(Serial number restarts from 01, record regression test delivery times)

(4) In the regression test process, if there is a bug, then in the development Branch (dev_20150804) modification, then the code merge to master, on the master tag to QA.

(5) After the test is completed, test issued test completion report, development on the last tag on the version of the release tag rel_20150804

(6) test report using Reg tag

(7) On-line problem repair, operation and maintenance must provide the current online label, development based on this label to establish hotfix branch

(8) If the hotfix has a regression version at the same time, the version can only be published on hotfix (exception flow)

(9) HOTFIX branch name rules with hot start, such as hot_xxxxxxx all kinds of test Reg, rel tag in the current hot branch, but also hot_xxxxxx_xx to distinguish

GIT Library Management specification