The maintenance of the Subversion has been more than 3 months. Although it is not a full-time maintenance Subversion, after the use of these time, it also has some experience.
In general, Subversion is really much better than CVS. Its protocol transparency does this do very well, you can pass the SVN's own agreement, or you can pass through the File Come access. Second, Subversion's permissions management will be handled by Apache (access to the Apache extension), so that Subversion can save a lot of workload when implementing, and does not need to learn one when the administrator needs to be used. New way. Furthermore, if you just want to browse the content on the Subversion, you don't need to update, you can access the URL directly from the Web Broswer, you can use it to be easy to use. SVN's command is also simple, in a Windows environment, there are a lot of easy-to-use Client tools, which is the most famous to TortoiseSVN, which is integrated with Windows Shell, use, very convenient, insufficient The place is that when the SVN work catalog is accessed, Explorer's reaction is relatively slow, which is also a universal shortcoming of shell integration (everyone must have a directory of Win XP with large ZIP files. EXPLORER RET I feel it.).
(Let's talk about the problem that the Subversion uses the problem of using the Subversion process.)
