Manage multiple versions of a project with SVN

Here's just a thought.

Common version Control tools:

The most commonly used version control in project development is SVN, Git, opensource, Google code, and so on.

Functional Features:

These versioning ideas are roughly the same, that is, there is a server to hold the resources of the submission, each developer to download the server resources to use their own machines, the modified content to be submitted to the server, so that other people can be updated to get your modified code or resources.

The differences between the various tools:

SVN is based on file system, in the Linux system or Windows system is the SVN to call the local file system to identify the changes, so that the user is updated or committed. Other version control tools, although not used, but from the introduction of this is not much different, generally have a client, similar to the network disk (the network is very limited in synchronization support, not suitable as a version control tool) of the same client.

There's something special about git:

Git seems to be good at dealing with version branches, which can only be created by the user in SVN, and then copied into the original, there is no way to do reference counting so convenient to reduce the number of copies. But at the moment the hard drive is so cheap it doesn't seem like a problem. But the drawback is that this stuff is managed across the ocean, and who knows how secure his security is. There is the command line operation, like to knock a long string of letters and can control the accuracy of the students must like.

SVN's Strengths:

Currently the most used guesses should be svn, sufficient for small and medium sized projects, the general SVN server is inside the company, the company's internal developers are maintaining the version. is also more convenient. The graphical interface, like managing local files, is fully compatible with the local file system and is used in the way you normally manage files. Ordinary users are also very easy to get started.

SVN manages multiple Versions:

As mentioned above, SVN manages multiple versions that require you to create folders on your own, typically because you already have a starter version that can be guaranteed to run, or there are a few forgiving bugs, but the project still needs to be improved, but there are also operational program support on site. You will need to create a suitable folder to hold the current version. The main purpose of this version is to provide a running version, so you can put the generated executable program and configuration to compress a file, source code (to prevent minor changes) and then compress one to put next. So you can drastically change the current version, there is a problem with the old version of the top. As for the catalogue organization, it is purely a matter of opinion, personal and project preferences, arrange it yourself.

Manage multiple versions of a project with SVN