Keywords: CVS, VSS, VERSION Control, Configuration Management System
Due to the open source and completely won the company's heart, CVS is used to use CVS in project development. But according to my understanding, CVS is not suitable for commercial companies. It is necessary to speak from the characteristics of CVS. CVS is originally for the development of source code projects, providing file version control functions. This type of project is: Set up a server on the Internet, each project participants can get the latest developments and documentation. Encourage everyone to develop any of these features and submit the code. In this way, there are a variety of code available for the same function. At this time, the project leader will see / compare the code submitted by each person and use one of them or submit an improved version on the basis of all versions. For the BUG that appears in the project, many people also encourage multiple people to submit different solutions, and the best one is selected by the project. The advantage of this is that the wisdom of everyone is concentrated. And the code submitted by everyone is saved in CVS, and everyone can exchange learning and promote improvement. This method of CVS is becoming a Copy-modify-merge. However, the situation of commercial software companies is not the case. For commercial software, several people must modify the same file at the same time, it is absolutely avoided, because it means duplication of labor, meaning the waste of human cost. Unless it is a competency test competition. In this regard, the version control software used by the commercial software company needs to prevent several people from simultaneously modifying the same file. A file-based version control software is very necessary for commercial software companies. Several version control software including VSS provides this feature. CVS did not provide this feature. The advocator of CVS includes the developer of CVS, regards the VSS's LOCK-Modify-Commit method as a backward development method, and regards CVS's Copy-Modify-Merge work mode as an advanced development method, obviously ignored business The actual features and needs of users. On the other hand, the Configuration Management system should not only just source code, and should also include development documentation. For UNIX / Linux users, most documentation is a text format. This is not a problem. Even if there are several people to modify, it can also be combined into a satisfactory document, reaching one by file comparison and merge function. good result. But for Windows users, most document materials are not text formats, such as Office documents, Visio documents, UML documents, er WIN documents, and more. For these documents, if there are two people to modify the same file, Copy-Modify-Merge works not to work. Because these files are not good, it is not good. In this case, you can only use one of the versions of one person, the version of others is invalid, and the new version is re-modified. Since I use CVS in the project, I often change a few people at the same time, and one document eventually leads to only one person's document, and others have to come back from the beginning. The worst, three people changed a Word file at the same time, and started to be submitted in the afternoon, three people were submitted, the problem was coming! Because everyone is modified, there is no continuous, if everyone starts to record it, which place it has changed, it is too much! I have been quarreled for a long time, let three people printed three, one word, another person records the revision, and it has been finalized for a long time. And hurt and gas: Everyone thinks that other people are not very good, why not let me? Ha ha.
