SVN source code management experience

Responsible and cautiously submit your own Code (Update first and then submit)
The SVN update principle is to be updated at any time and submitted at any time. When a small feature is completed, it can be compiled and tested by itself, and then submitted with caution.
If a conflict occurs during the submission process, contact the previous developer and negotiate with them to resolve the conflict. After the conflict is resolved, the two must test together to ensure that the conflict is resolved, Program Other functions are not affected.
If an update is generated during the submission process, you also need to re-compile and complete some necessary tests before submitting.
Atomic commit
The interval of each submission is as short as possible. The development work should be one hour or two hours. For example, when you change the UI, you can submit the UI once every time you modify or design the UI. When developing a function module, you can submit each time you test a small-Detail function. When modifying a bug, you can modify a bug and confirm that the bug has been modified, it will be submitted once. We advocate multiple submissions, so we can add insurance for code.
Do not submit automatically generated files
Visual Studio generates many automatic files, such. suo and other configuration files, debug, release, OBJ, and other files that are automatically generated and irrelevant to the compilation code should not be checked in upon submission, if you accidentally check in, you need to use the DELETE command to delete from the repository. You can use the svn filter function to set ignore lists in the settings.
Do not submit code that cannot be compiled
Before submitting the code, make sure that you can compile it locally. If a third-party class library is used in the code, consider that some members of the project team may not have installed the corresponding third-party class library or are not put into the GAC (.. NET Framework), when preparing the project work area, the project manager must consider this situation to ensure that the development team members can compile the code in a unified environment after checking out the code.
Do not submit code that you do not understand
After the code is submitted to SVN, your code will be shared by the project members. If you submit code that you do not understand, you cannot understand it, and others cannot understand it. If you encounter problems in the future, it will become a risk of project quality. Therefore, before introducing any third-party code, make sure you have a clear understanding of this Code.
Announce your work plan in advance
Before you begin to modify a function, let the team members talk about your change plan, so that everyone can understand your thoughts and your upcoming changes to the software, in this way, possible conflicts in the development process can be minimized to improve development efficiency. At the same time, you can also find out your previous design deficiencies in your communication with members and improve your design.
Clearly mark submitted information
+) Indicates that the function is added.
*) Indicates that some features have been modified.
-) Indicates that the file has been deleted, or some features have been cropped, deleted, and blocked.
B) indicates that a specific bug has been fixed.
Source code It is an important part of project management during management, and it is important to find that testing is true. Dedicated testers are required.
From. Net Eden http://aspx1314.cn.
, Original address: http://aspx1314.cn/archives/747.html