Use cases for the SVN directory-(Backup, branch, merge)

SVN directory use case:

A team plans to develop a "Mo Mo" project
Part of the base code is already in the early stages of this project
Research and development team in this basic code after 3 months of effort, developed a relatively complete V1.0 version of the launch promotion, and achieved good results (backup to tags)
As the market feedback was good, the team began to work on the development of the V2.0 version
In the development of the V2.0 version, it is found that there is a serious bug in the V1.0 version, which will cause serious consequences if not modified in time.
After the development team receives the bug report, it immediately arranges for the V1.0 version to be repaired, but other developers continue to develop the new features of the V2.0 version
The person who fixed the bug quickly found the cause of the problem and fixed the problem, and released the V1.1 version for the user to upgrade, so there was no significant loss
After a bug fix, the developer integrates the repaired code into the development line so that it does not occur again in subsequent releases later on
In this way, the whole team in the joint efforts of everyone, methodically carried out ...

1. If a version is developed and has been committed, you need to back up the version and add her to the tags folder.

It is recommended that you refresh the remote repository between backups (Command + R)

2. Name the backup file and back up to the tags folder

3. Annotate the backup file

4. If a backup file already exists under the tags folder

5. At this point, the team can continue to develop version 2.0 on the trunk (trunk) in version 1.0, as the original 1.0 version has been backed up into tags

6. If you find that the 1.0 version has a bug, then you can give tags in the 1.0 version of the backup project to open a branch (branch), the branch project check out. Fix bugs in the branch (do not fixbug directly in the backup, otherwise the backup will be gone)

After the 7.bug repair is complete, you need to release the repaired version 1.1. Then add the 1.1 version to the tags for backup. Finally merge the 1.1 version with the 2.0 version being developed, then merge the 2.0commit to the server.

8. Delete the version in the branch

Use cases for the SVN directory-(Backup, branch, merge)