Apache Subversion vs Azure DevOps Server (formerly TMS)

• Version control - it's what it's designed for.
• Modifiable - It only takes a little bit of knowledge of a scripting language (I used Windows BAT files calling Perl scripts) to extend capabilities, like the aforementioned integration with Redmine.
• Back end administration- It's a breeze. There's very little work involved in terms of administering it once you've got it installed on a server, and even setting that up isn't bad.

Read full review

• The consolidation of issues is extremely useful for us. Having one place where all bugs are entered has helped our business process immensely.
• Being able to query data regarding user stories, bugs and code is extremely helpful. As well, using the visual tools built into the system can help with messaging regarding the status of a project.
• Being able to monitor code deployments is extremely helpful. Since we are managing multiple environments, this tool makes it easy to see what is happening where.

Read full review

• At times, locking problems can be difficult to solve. This normally happens you make a mistake, like attempting to update a folder that has running executables within it. Often times, you can just unlock a parent folder and you' are all set, but on more than one occasion I have had to recheckout a folder because I could not resolve the lock, even after rebooting.
• Looking up the history of a file can be very slow, taking several minutes, especially when looking at the history of an entire folder.
• Novice users of subversion often make the mistake of dragging folders in Windows that are managed by subversion. This does not cause the folder to move in the svn repository, which can lead to serious confusion why a user's folder structure does not seem the synchronize correctly with other users. To an advanced user, this can be a very useful feature, but absolutely hell for the novice.
• I have not found any third-party tools yet that let me visualize the commits for a codebase, particularly across branches. This may be partially because of the slow history I already pointed out, but I believe it's because I have not been willing to even look at the multi-thousand dollar code management solutions I have seen advertisements for in the past.

Read full review

• The older versions of TFS are more lacking in the web version-- if you aren't updated to 2015 or above I believe, a lot of the web features are not available (like bulk update). You really have to keep up to date with TFS for the best features, and it's no simple task to migrate your entire instance of TFS from an older version to a newer version.
• VSTS is supposed to be a virtual version of TFS that we've been looking into, but it severely limits customization options for ticket templates and workflows. It would be nice for VSTS to eventually carry that customization over so we could feel more comfortable switching to "the cloud" so to speak.
• Queries are a very powerful tool, but normal business users struggle to understand how they can best utilize this tool to analyze tickets. Because of the permissions structure in all companies I have been a part of, I've never been able to save my custom queries to a public folder in TFS for business/project users. Instead, I have to take time to train these users and give them guidance on how to best create queries for their needs. This is admittedly a business process issue, but it could potentially also be resolved with some good training/guidance around queries provided by TFS themselves.

Read full review

• I cannot speak on ROI but Apache Subversion is definitely the best version control tool for a project of any size. It serves the user's purpose in a complete satisfactory way.
• As it is open source, there is no need to spend any amount on it, which makes it an even more easier choice.
• The most negative impact Apache Subversion can have on you is that you will not want to use any other version control tool after using it.

Read full review

• Time to completion for projects has significantly gone down by 15% and that number changes as more people are trained and are comfortable with TFS.
• Change Management and Approvals are easier to access.
• More projects are implementing SCRUM methodologies for applications

Read full review