Apache Subversion Reviews and Ratings

Use Cases and Deployment Scope

Our web development team uses Apache Subversion as one of our version control systems. A version control system is a critical tool for software development because it provides a central repository for our shared code and also tracks how our code changes over time, allowing us to view a history of changes or revert back to a previous version if necessary.

Likelihood to Recommend

<div>It's a relatively simple version control system so it works great for an individual or small team (less than 10 people). But if you have a medium to large team, especially one with members distributed over a large geographic area, or one where individuals need to be able to work "offline" without access to a central server, Apache Subversion will likely not be the best choice.</div><div>

</div><div>Also, if you're maintaining an open-source project where outside people will be interacting with your code repository, git is probably a better choice because it's becoming the de-facto standard these days and what most developers are familiar with.

</div>

Use Cases and Deployment Scope

Used mainly as a collective tool for version tracking to ensure revisions are tracked by the dev team, and all maintain branches of our team/project repositories. To commit the revisions once all devs have merged code from respective timelines.

Likelihood to Recommend

Can be [suited] for teams building solutions and manage code file versioning. Subversion for us simplifies the changes per file and code version before merging to branch for continuous integration and eventually deployment. With Apache Subversion in the process of our agile development, we can continue to automate deployment as much as possible with versioning.

Use Cases and Deployment Scope

We used Apache Subversion to manage and control source code for our development team. Subversion helps to track, version, and manage conflicts when a file is being worked on by different team members at the same time. It allows changes to happen in parallel, keeps track of exactly what, when, and who has made the change, and allows us to revert back if necessary.

Likelihood to Recommend

Generally speaking, distributed version control systems (DVCS) such as Git have taken over the version control market (e.g. Github), but if your organization is mostly centrally located and is not already using something like Git, SVN can still get the job done and do it well.

Use Cases and Deployment Scope

We used to use Apache SVN for source code file versioning for all our software projects in the e-business department. Now we only use it for few projects that are not transitioned yet to Git. SVN, as most of the file versioning tools provide the following for us:

<ul><li>Revision control.</li><li>Interactive conflict resolution.</li><li>Tracking commits.</li><li>Collaborative commits (with the ability to lock files for disabling collaboration and avoid conflicts).</li></ul>

Likelihood to Recommend

Subversion solves our software versioning problem by providing tools for conflict resolution when doing collaborative work on the same files and projects. We use it with TortoiseSVN and it works great for some of our projects with smaller teams. However, we have a need to make code reviews more and it is a little more difficult to do that in SVN, compared to Bitbucket and Git.

Use Cases and Deployment Scope

Subversion is being used by our engineering team to manage the development code we write for the company.

Likelihood to Recommend

Where multiple developers have well-defined areas of responsibility it works great! When many developers are all working in the same area of code, so changes overlap, then it is more of a challenge. But, like Git, it has pretty good merge tools to help resolve conflicts.

Use Cases and Deployment Scope

In my organization, Apache Subversion (SVN) is used as a versioning software for some specific types of objects. It is always and only used to allow the multiple processing of objects avoiding that a resource overwrites more recent changes and to keep track of the last changes made so as to go back to the previous modification and evaluate the differences.

Likelihood to Recommend

If you have multiple development environments and different resources involved; if you have more developers accessing the same files and the changes are continuous (for example if you are in a continuous delivery condition) it is certainly advisable to implement a versioning solution and SVN is a good product certainly.

Use Cases and Deployment Scope

We used Subversion to manage a ColdFusion based software development project for a US Federal government contract. We were largely isolated (both geographically and organizationally) from the rest of the company (it was their attempt to get into Federal contracting) and I'm not sure what was used in other parts.

Our biggest reason for using it was to allow working on multiple releases in parallel. Before I helped set up Subversion properly, they were delivering old code with new releases, "clobbering", as they said, previously delivered code. By setting up proper branching, I fixed the problem, to the relief of both the company and the customer.

I also integrated it with the Redmine issue tracking system, requiring developers to associate issues with their commits.

Likelihood to Recommend

I'd recommend Subversion for almost any software development effort. It is less appropriate for any project with widely geographically distributed developers. For VERY elaborate projects, a higher end commercial tool might be warranted.

Use Cases and Deployment Scope

I have used apache subversion for a course that I have taken and also for a company that I intern for. It is used for collaborating projects with team members. At the university level, apache subversion is a mandatory version control [solution] to be used in many courses and an option in many other courses in the fields related to computers. At an organizational level, at the company that I currently intern for, apache subversion is used by the whole software department over 3 different countries to collaborate over the huge project we are working on. Apache Subversion is a simple tool used to keep all the people working on a project on the same page by letting everybody work on the same project at the same time.

Likelihood to Recommend

I would recommend using Apache subversion for any kind of project no matter the size or type of the project. It is very well suited in scenarios where the project is being worked upon by a team, especially a large team operating over various time zones. It provides a good means of collaboration among team members, allowing them to work peacefully and time effectively. I do not recommend using apache subversion for projects that are solely documentation based because it would be an overkill. Instead you could use Google Drive for such projects.

Use Cases and Deployment Scope

Subversion used to be our main version control software before we started using GitHub. But after introduction of Git, we stopped using subversion drastically . We only have a few old code projects which are still on subversion. We have decided to go ahead with Git for all new projects.

Likelihood to Recommend

If the code versioning is only needed between a few developers (with not much collaboration) and company cannot afford to buy GitHub License.

Likelihood to Recommend

I would only consider not recommending Subversion if the development department adheres to what I call the "One Microsoft Way" (a play on words of Microsoft's address). Many IT departments prefer to go completely by the book on all procedures related to IT. While that is justifiable if you consider what to do if the entire programming department quit without notice, Subversion offers too many advantages to not consider seriously as a better replacement for Microsoft's standard source code repository solutions.