Apache Subversion is a version control option that is free to download and open source under the Apache 2.0 license.
N/A
Buddy
Score 9.0 out of 10
N/A
Buddy (formerly Springloops) is a SVN/Git source code management tool focused on web development teams. It allows users to code in parallel and share code safely concentrating on results, not on lost changes or overwritten files. With quick deployments, users get rapid collaboration in protected space.
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.
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.
Springloops is the best tool for deployment to any environment. Especially, the auto-deployment feature on development servers is essential for the early stages of development. The built-in source control mechanisms are a perfect combination of ease of use and a rich feature set that allows the development team to have an easier and more complete view of each part of the project. A section that is lacking is time tracking - but then this is not the main usage of the service.
Distributed development - I've never worked in an environment where distributed development (developers widely scattered geographically) was a factor, but that's why git exists.
Merging - Merging of code from one branch to another can be painful, especially if it's not done frequently. (On the other hand, doing merges is one of the reasons I get a nice salary, so I can't complain too much!)
Acceptance - Let's face it, git is what "all the cool kids are using." If you've got a bunch of developers fresh out of school, they'll probably know git and not Subversion.
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.
Apart from being a great versioning control system Springloops offers the options to automatically deploy code to multiple systems. This feature alone is a determining factor to renew Springloops over and over again. Another important factor is that it offers a full set of tools that help the team during the development cycle. No switching between time-tracking to project management. This is a real time-saver.
Easy to use, automatic deployments, comments on projects are only a few factors. Multiple servers per project is another must-have feature. User permissions and rights offer granular control on access to the system
I rarely use it but when I need it the team is there. During the initial steps of Springloops, I had close contact with one of the founders. He provided support to me over Skype! He didn't have to but he did. We had a couple of long talks about some issues I was facing. He has there regardless of time. It was a great experience
Git has become the new standard of version control, with its support for distributed design. As a tool to manage and control versions, Subversion does it well, but Git is the future.
Springloops has a built-in feature that is lacking from Bitbucket (at least on the out-of-the-box functionality). Deployment of projects to various servers/development stages. The process is so easy and painless that even remote servers can act as local environments. This is a feature that differentiates Springloops from other solutions that require other tools to perform the same task.
