Version control of Agile Development

What kind of Project version control tool are you using?

Now the more popular version control has parallel (SVN), distributed (Git), streaming project versioning.
what principles or specifications do you generally need to know about using version control? Frequent check-in and check-out

In agile development, code-sharing, frequent check-in and check-out, and everyone on the team can see each change

There is also a benefit to reducing the frequency of version conflicts
Note Details

Detailed comments, should be a description of each update or new content, so as to facilitate the review code when easy to locate how the function point
version control of most content

such as source code, environment configuration, script management, and so on, these version control, you can control and restore each change

It is not recommended to put the compiled binaries into version control because the compiled files are generally large and can be recompiled when the system is built automatically

It is not recommended to include dependent third-party tool classes in version control because the tool class can be specified when the system is built automatically
What kind of development mode do you use? Branch Development

The branching development referred to here refers to the development of feature branching, which ensures the continuation of the backbone, without the need for a way to hide the feature.

The development cycle of an attribute branch cannot be too long, preferably not more than one iteration cycle

Frequent merging of changes in the trunk into feature branches

Attribute branches merge into the trunk, paying special attention to merging feature branches before merging them.

Creating team branches by team is not advocated, which results in frequent test acceptance for each team branch merging into the backbone
Backbone Development

Ensures that all code is continuously integrated to ensure that developers have access to the team's code for members, avoiding the disaster caused by project consolidation and integration

Backbone development can create a branch by publication, after the release branch is released, on the release branch, the bug fix code is merged into the trunk, and the release branch is only severely flawed repair