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 PTC Integrity is an excellent source code management and version control tool, and I would suggest anyone to use it for that purpose. We can even define our workflows using individual forms for implementing Change Management, Defect Management and Access management requests. If properly used, this tool is great for managing our code for very long periods, considering my 4-5 years of usage. Though the UI could be better, and integration with some application servers could be better implemented, this tool is a good tool.
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 Helps to advance carefully through complicated and delicate process hives. Improve thereby our time-to-market knowledge transfers along our portfolio. Enhances the performances of single step in processes as well as the processes. Allows for unprecedented overview in broads and in depths. Steffen Jäschke Projektspezialist bei Steffen Jäschke EinzUnt Physik, Berechnungen
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 It can be overwhelming with the number of tabs, functions and ways to achieve the same result. The average user may struggle with learning the tool. The text editing in Integrity is weak and does not provide many options. Because of this, many user decide to use MS word instead, to document requirements. 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 I do not make decisions on what tool my company uses. I am just the user of the tool and such decisions are not handled by me. If I were to make such decisions, I would definitely renew MKS, considering the amount of data we have stored in MKS and the current number of users who are familiar with the system
Read full review Usability PTC Integrity comparatively could be considered a nice Source code management, Version controlling tool and could be compared with tools like StarTeam. If the integration to move/migrate code could be integrated into this tool, it would become an extremely powerful tool.
Read full review Support Rating PTC Integrity administration can be somewhat daunting. They have been able to help with every question that I have submitted. Their support website is very easy to understand and submit questions and their phone support is wonderful
Read full review Implementation Rating I wasn't involved in implementation.
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 I think the reason that PTC Integrity was initially chosen is that it was the best product available in the mix at the time. This coupled with the PTC deal on multiple products was a no brainer based on the size and scope of potential users.
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 MKS Integrity has proved to be particularly useful in the software development process by increasing employee effieciency MKS integrity has also made software development a very efficient process and makes feature releases and bug fixing a lot easier In addition to the above, our organization has been able to support manufacturing easily by reverting to a previous software version in case of an emergency. It has also led to faster time to market for new products. Read full review ScreenShots