Old but rock-solid version control solution
March 25, 2021

Old but rock-solid version control solution

Anonymous | TrustRadius Reviewer
Score 7 out of 10
Vetted Review
Verified User
Review Source

Overall Satisfaction with Apache Subversion

We used Subversion (SVN) as our development team's version control system. All source code, assets such as images are stored and managed by SVN. It allows different team members to work on the same code file in parallel, for example, one working on a bug fix while another working on the new feature enhancement, without having to worry about interfering with each other's work. Once completed, changes from different team members can be merged in together when ready. SVN also help tracking each change made to the files, allowing for each traceability when needed.
  • Manage different version of tracked files.
  • Has great support from other development tools and systems.
  • Well documented and maintained.
  • Great ecosystem and online communities.
  • Does not support the more modern de-centralized model.
  • Does not have features such as pull requests, which is key for open source development.
  • Can sometimes be slow, especially with large repositories.
  • Improve developer productivity by allowing development happen in parallel.
  • Tracking down bugs easier by providing visibility into the entire change history of the code repository.
We chose SVN over the other alternatives due to it having better tool support and integrations with our other development systems such as Atlassian Jira, and Bamboo. Developers are also more familiar with SVN and there are more resources available online if we ever run into any problems.

Do you think Apache Subversion delivers good value for the price?

Yes

Are you happy with Apache Subversion's feature set?

Yes

Did Apache Subversion live up to sales and marketing promises?

Yes

Did implementation of Apache Subversion go as expected?

Yes

Would you buy Apache Subversion again?

No

Any development team would need a version control system. If your organization is using something older such as CVS, then you should really consider upgrading to SVN. However, if your organization does not have a version control system and is starting from scratch, then I would highly recommend using Git instead.