QuickStart with Subversion

In software development, using a revision/version control system (VCS), such as Subversion, is highly recommended. A revision control system should make each developer's life much easier, whether you're an individual developer, or a team of developers.

These instructions provide a step-by-step walk through of getting a new project into Subversion. They assume that you have Subversion (command line) already installed.

Why Subversion?

If you're evaluating a VCS for your organization, you should note that Subversion isn't the only product on the market. Subversion has seen increasing popularity, and has become the defacto "default" for many projects. It is used by the AppFuse product, and, as an example of its ubiquity, its server and client tools are now bundled by default in Mac OS X (10.5+).

Before making the leap though - especially if you're a larger team - you will want to make sure that it's the most appropriate tool for your organization. Alternative tools that are also open-source:

• [http://git.or.cz/]: distributed VCS, GPL v2 licensed.
• [http://www.selenic.com/mercurial/]: distributed VCS, written in Python; GPL licensed.
• [http://ximbiot.com/cvs/wiki/]: GPL licensed; still widely used, but seen as deprecated by many developers, in favor of Subversion.

There are also many commercial tools available: [http://www.perforce.com/], [http://www.bitkeeper.com/], and Microsoft's [http://msdn2.microsoft.com/en-us/teamsystem/default.aspx] amongst the most popular.

That said, if you're an individual developer, its . In any case, NO VERSION CONTROL SYSTEM is definitely worse than one.

Create your Subversion Repository