Apache Subversion vs. Beanstalk

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.

Incentivized

For business or personal applications, where you wish your code to remain private and/or proprietary, Beanstalk could be a good fit. If you are also interested in beginning to automate with relative ease, their tools can be a great help. Code reviews can also be a key factor in the decision, as they provide a good framework for accountability.

Incentivized

• Track and control concurrent versions of the same files.
• Has good support from many different software, including visualization, DevOps toolchain.
• Well documented and understood by developers as it has been around for a long time.

Incentivized

• Automation
• Code Review
• Support

Incentivized

• Refactoring the layout of a respoitory--or a part of a repository--can be a bit painful, especially for users with workspaces associated with the affected part of the repository. Not sure what could be done to make that better, but it would be nice if something was possible.
• Folks coming from Git can have problems using Subversion. Again, not sure anything can (or should) be done to address that, but it is occasionally an issue.

Incentivized

• Interface is not always intuitive, some areas are easier than others to navigate.
• Price plans are a little odd. However, they do seem to be flexible if a plan does not quite fit your needs.

Incentivized

While there are interesting alternatives, such a GIT, Subversion has been a breath of fresh air compared to its predecessors like CVS or Microsoft Source Safe (now called Team Foundation Server). Its ease of use and high adoption rate is going to keep me using this product for years to come.

After Microsoft Visual SourceSafe was discontinued, we chose Subversion and it was a great choice. We were able to migrate to Apache Subversion very quickly and easily and benefited immediately from its non-locking workflow (SourceSafe required users to "lock" the file when editing to prevent editing conflicts from other users, whereas Subversion allows multiple users to edit the same file simultaneously and then merge conflicts later.)

While we still use Apache Subversion for our legacy projects, we've migrated to Git and GitHub for our new projects as that is the new "cool kid" and it provides some benefits such as distributed and offline development. But Git is more complex than Apache Subversion and not as easy to learn.

Incentivized

If you are creating open source applications, there is almost no reason not to use GitHub. If you do need private repositories (for proprietary or private, business or personal use), Bitbucket could be an excellent solution. Beanstalk's main advantages lie in the support (which is excellent), deployment tools, and code review features.

Incentivized

• It allowed us to deliver the right files to our customer without "clobbering" previous releases, making for a far more satisfied customer.
• It allowed our developers to work on two releases in parallel (plus an occasional third, for emergency fixes).
• With some simple hooks, it allowed us to set up a system where code was was automatically deployed to test servers as soon as developers committed it, making testing easier. This was made easier by virtue of being a ColdFusion project, which requires no compilation. However, that is possible for compiled code with a continuous integration system like Jenkins.

Incentivized

• Increased automation => better accuracy and efficiency of maintenance/launches
• Better insights into ongoing work and past modifications to code => lower chance of error and more efficient troubleshooting

Incentivized