Centralized control of SCM is important to some people. The URL scheme is easy to manage and user management with Apache integration means I rarely worry about users.

Review collected by and hosted on G2.com.

Branch management is terrible. Built-in merge isn't much better.

Basically, very few modern repositories use Subversion. Most have gone to distributed systems from centralized ones. Review collected by and hosted on G2.com.

I enjoyed the speed most of all, and the overal design of the platform Review collected by and hosted on G2.com.

Did not get quickly to set up my environment, after thtat though had a good experience overall Review collected by and hosted on G2.com.

Having used a number of different version control systems, I would always consider Subversion for a general purpose SCM. It works very well with teams of varying skill set, where the individual developers need supervision, training and review, as may be the case with trainees, juniors, contractors and overseas developers. Centralized SCM means the leads and seniors are in control and can review work and manage processes such as CI, build, test automation and delivery. Subversion is free and open source software with a mature feature set, and a large number of client integrations and tools.

Despite claims to the contrary, multi-site configurations with Subversions are both simple to set up and robust to operate.

In Subversion, there is usually one way to do something, and to do it right. If that way is followed, the user will be blessed with success. Review collected by and hosted on G2.com.

Subversion's strengths may turn into a weakness when a distributed SCM is required. These are more popular in teams composed of highly skilled, individually motivated contributors. The reader must decide whether this is the case. For most professional development teams the point is moot, and subversion's maturity may be the deciding factory. Review collected by and hosted on G2.com.

easy to control the source code in a team in different areas Review collected by and hosted on G2.com.

can't fetch the log of a branch few years before. I work on a program from 2012, and can't fetch the log of a branch of a project sometime. Review collected by and hosted on G2.com.

It's highly functional, and easy to use. There is little concern as far as getting it setup or working. Works great across multiple OS and environments. Review collected by and hosted on G2.com.

It's not the fastest, easiest to integrate, or even the most versatile repository management software. Review collected by and hosted on G2.com.

Our version of SVN has integrated Windows support, so unlike like git, there is no need to push and pull code through a command line interface. Review collected by and hosted on G2.com.

There is a little bit of a learning curve when using SVN through the Windows interface, but it is still easier than git. Review collected by and hosted on G2.com.

- easy to learn

- easy to setup on own environment

- flexibility in setup (configure hocks, access privileges etc.)

- good GUIs (Versions.app etc.) Review collected by and hosted on G2.com.

- commit conflicts

- performance in general

- repository size Review collected by and hosted on G2.com.

Newer system based on CVS, Includes atomic operations, Cheaper branch operations, Wide variety of plug-ins for IDEs, Does not use peer-to-peer model. Review collected by and hosted on G2.com.

Still contains bugs relating to renaming files and directories, Insufficient repository management commands, Slower comparative speed Review collected by and hosted on G2.com.

Like any version control system, I liked the ability to maintain a single copy of documentation (requirement docs, data models, etc.), rather than having 10 copies of the same document, each with a different "version" number. Subversion provides a "lock" safeguard to prevent multiple people from making updates to the same item at the same time. I found it fairly simple to be able to locate the previous version of a document. Review collected by and hosted on G2.com.

Since you maintain a "working copy" on your desktop, I've broken the fragile link between the desktop app and the online repository. I've broken Subversion about every way possible, and learned how to manually remove the "sync" feature for the folders in my Subversion repository so that I could re-sync my folders properly. In my organization, I found that few people actually used the lock feature before making changes. I found that the merge feature wasn't as robust as I would have liked. If I'm merging a Microsoft Excel spreadsheet with another similar Microsoft Excel spreadsheet, I'd expect that to work. Review collected by and hosted on G2.com.

Very basic, very simple. Command line mode does everything you need. Nothing complicated about it. Review collected by and hosted on G2.com.

No real workflow and it doesn't tie into other systems. If you need something quick and easy, subversion is your best bet. Review collected by and hosted on G2.com.