Version Control for agile development

• Which project version control tool is used?

Currently, popular version control methods include parallel (SVN), distributed (GIT), and streaming project version control.

• What principles or specifications do I need to know when using version control?

• Frequent incoming and outgoing checks

In Agile development, code is shared and frequently checked in and checked out. All the people in the team can see each change.

Another advantage is that it reduces the frequency of version conflicts.

• Remarks

The detailed remarks should be the description of each update or addition, which is helpful for locating functions easily during review code.

• Versioning most of the content

For example, source code, Environment configuration, script management, etc. version control can be implemented to control and restore each change.

It is not recommended to put compiled binary files into version control, because the compiled files are generally large and can be re-compiled during automated system building.

Third-party dependent tool classes are not recommended for version control because the tool classes can be specified during automated system building.

• Which development mode is used?

• Branch Development

The branch development mentioned here refers to the feature branch development, which can ensure the continuous release of the trunk without feature hiding.

The development cycle of the feature branch cannot be too long, and it is best not to exceed an iteration cycle

Frequently merge changes on the trunk into the feature Branch

Feature branches are merged to the trunk. Note that feature branches are merged only after feature branches are accepted.

It is not recommended to create team branches by team. As a result, the branches of each team are merged into the trunk for frequent Test acceptance.

• Trunk Development

It can ensure continuous integration of all codes and ensure that developers can obtain code from members of the Group to avoid the disaster caused by project consolidation and integration.

The master development can create branches by publishing. After the branch is released, the codes that fix the defects on the branch are merged into the master, and only the severe defects are repaired on the branch.