The main new feature of VisualSVN Server 3.3 is the full support of Subversion’s locking for distributed VDFS repositories. Other significant changes include improved performance of commit to slave VDFS repositories and further optimization of VDFS replication over the WAN.
Starting from VisualSVN Server 3.3, distributed VDFS repositories become functionally equivalent to regular Subversion FSFS repositories. End-users can perform all possible Subversion operations with master and slave VDFS repositories — checking out and updating working copies, committing changes, modifying revision properties, locking and unlocking files, etc. This makes the migration to distributed VDFS repositories completely transparent for end-users.
Upgrade to VisualSVN Server 3.3 is recommended for all users. Upgrade is easy and straightforward, but it is highly recommended to read the KB85: Upgrading to VisualSVN Server 3.3 article beforehand (especially if you are upgrading from versions older than VisualSVN Server 3.0).
Subversion’s locking support for VDFS repositories
VisualSVN Server 3.3 provides full support of Subversion locks for distributed VDFS repositories. Locking and unlocking can be done through both master and slave repositories. These operations are guaranteed to be consistent and the locks themselves are replicated between the repositories in a very efficient way.
Other VisualSVN Server 3.3 changes
VisualSVN Server 3.3 introduces a few other functional and performance improvements, such as the following:
- Improved performance of commit to slave VDFS repository. Commits of large files to a local slave VDFS repository are now completed significantly faster than over-the-WAN commits to a remote Subversion repository.
- Further optimization of VDFS replication over the WAN. With the latest TCP settings optimizations, VisualSVN Distributed File System is able to fully utilize 100 Mbps WAN link when data is replicated between master and slave repositories.
- Automatic handling of intermediate certificate authorities (CAs) required to verify imported SSL certificates.
For the complete list of changes, see the VisualSVN Server 3.3.0 changelog.
Upgrade and compatibility concerns
Upgrade to VisualSVN Server 3.3 is recommended for all users. Read the KB85: Upgrading to VisualSVN Server 3.3 article before upgrading. Upgrade is free for Standard Edition users and all customers who have an active maintenance subscription for VisualSVN Server Enterprise Edition licenses.
You should consider a specific upgrade procedure if you are using VisualSVN Server 3.0 or newer and have distributed repositories based on VisualSVN Distributed File System. Read the KB86: Upgrading to VisualSVN Server 3.3 in a multisite environment for further details.