We recently hosted a panel of Apache Subversion thought leaders, experts and developers, all with a vested interest in the future of SVN. If you missed it, check out the blog here. You can also watch the full replay below.
In it, we talked about Subversion, where it is and where it’s going. The discussion leaves us begging the question- Is SVN stale, outdated or obsolete?
Let’s address the elephant in the room
Yes, SVN needs some updating.
Assembla has been steering that ship, with a motivated community of developers behind us. In the coming days and weeks, we are excited to share the work we’ve done to update SVN into a modernized version control system.
What is “NextGen SVN™”?
SVN Devs and C-Levels want mobile access and feature parity to other systems, but still need security and compliance assurances of a central repository. This is NextGen SVN™. We’re recognizing that the cloud has won. CIOs aren’t running to purchase servers to stick in a dusty storage closet within their offices. They are looking for secure ways to utilize the cloud.
We’ve recognized that security is the big non-negotiable. According to financial analyst firm Piper Jaffray, data breaches are up 18.5% in 2017. It’s obvious that these threats aren’t going away, and it’s more important than ever to stay on top of leading edge security advancements, especially where code is involved. Assembla’s NextGen SVN offers granular access control and audit logs that give total visibility into user activity against the central SVN repo. Other versioning systems don’t offer this level of auditability.
While SVN might not be the right fit for all code, we feel that it is the right place to store mission critical code. In other words, SVN is for anything essential to business operations or an organization’s viability. Think intellectual property or revenue generation.
Over the next few weeks, we’ll be sharing more about the NextGen SVN™ portfolio as a combination of new features with increased ecosystem investment focusing on compliance and security.