SVN experience 3

21. Store all development code on trunk.

Common branch modes:

A. Release branch: when the Code develops to a certain stage, a release branch is established, the current version is retrieved, and copied to the branches directory for a comprehensive and rigorous test, if any bug is found, it will be repaired in the current version, and the bug in trunk will be synchronously updated. After testing, copy the file to the tags directory and publish it to the customer.

B. Feature branch: If complex modifications are required, it will affect the stability of the trunk code. We recommend that you create a feature branch and merge it with the truck trunk after the features are stable.

22. Tag: it is a snapshot of a project at a certain time. This is a common term. Each submission of a revised version is actually a precise snapshot.

 

23. layout of common classic version libraries:

For a single project, the following format is recommended:

/Trunk saves the main line of project development.

/Branches saves various development branches of the project.

/Tags saves the project tag, that is, the branch that will never be modified after the project is created, such as releasing the release version.

If multiple projects are in the same version library, the following format is recommended:

/Rigtms/trunk

/Rigtms/branches

/Rigtms/tags

/Docprotect/trunk

/Docprotect/branches

/Docprotect/tags

Note ** individuals tend to use the first method. One is that the format is relatively simple, end users are not easy to confuse, and the other is that the permission control of the version library is relatively simple, third, subsequent backup/restoration is relatively easy

24. SVN data storage formats include Berkeley dB and fsfs. By default, the version we are using is data storage in the fsfs format.

 

25. SVN built-in tools

(To use these tools, you can enter commands such as svnadmin help and svnlook help in command line mode)

Svnadmin: Provides the SVN version Library Creation function and can be used to maintain these version libraries.

Svnlook: Used to view different revisions and transactions in the version Library (it does not change the version content ).

Svndumpfilter: it can be used as a path-based filter for SVN version database history.

Svnsync: transfers the history of one version library to another. This feature allows remote operations ("Source", "target" version libraries, and svnsysnc programs can be used on different computers .)

 

26. Main Methods for SVN to save disk space:

1. incremental technology is used to record only one of the two groups of data. The other group only stores the difference from the first group.

2. Due to network exceptions on the client and server, or abnormal suspension of the client SVN process, the transaction committed by the file may fail and the transaction unexpectedly aborted can be deleted. You can use $ svnadmin lstxns myrepos to clear the logs.

 

27. delete unused Berkeley dB log files

Svnadmin list-unused-dblogs/path/to/Repos

Rm 'svnadmin list-unused-dblogs/path/to/repos'