Likelihood to Recommend 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.
Read full review Very slow and not intuitive; it would be my last choice for version control systems.The UI is a little confusing at times and seems a little outdated. It needs a lot of improvement. It is suited for small projects and fewer number of projects. But if there are huge projects and many projects to be maintained in a portfolio, its a little hard to manage.
Read full review Pros Revision control done properly - you have end to end visibility of all changes in the project. Conflict resolution - visually highlighting the differences helps to track down the problem. Being open source and very popular. We are using SVN hosted in our network - it is very stable, we had almost zero downtime in 4 years. Rollbacks are made simple and easy to use. Read full review One place for most recent code with history, avoid any conflict/confusion among other team/members. Stream/Workflow approach to control approval process betwen all the teams, which I couldn't find in other version control tools I worked. Bundle our code in a small group (called, Issues in Accurev) to differentiate between different projects. Read full review Cons 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. Read full review Ability to zoom in/out for stream-view. We currently have many streams/substreams and unable to view the entire workflow. Zooming in/out would benefit. Being a designer, I use Adobe Flash and SWF files. When updating the SWF files, Accurev does not see these files as being changed and you will be unable to promote. In order to push changes, you must totally rename the SWF file. Read full review Likelihood to Renew 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.
Read full review We will renew because it is part of our build process.
Read full review Alternatives Considered 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.
Read full review In my view, accurev ranks very low compared to other tools I have used. Microsoft
TFS is the best in the industry as of today as it's a complete ALM solution. It does code version, bug tracking, user story documentation, and has easy integration with other external tools supporting many languages. So I would definitely recommend
TFS to anyone.
Read full review Return on Investment Subversion helps us feel secure in maintaining access to all of our product code, both current and historical. Being free and open source makes it an even better "investment". Read full review Better team coordination. Avoid confusion by having one place for all documentation and code. Better project management by having different work streams. Read full review ScreenShots