This post is from the CollabNet VersionOne blog and has not been updated since the original publish date.
Subversion Edge 4.0 Released
Hopefully you saw Mike’s post yesterday about the release of Subversion 1.8. Congratulations to the Subversion team on the new release. Today I am pleased to announce the release of Subversion Edge 4.0. This is the release that delivers Subversion 1.8 to your servers so that you can take advantage of the new features offered by Subversion on the server. We are also taking this opportunity to upgrade our Apache HTTP Server stack from 2.2 to 2.4. This will allow you to get the most out of your Subversion 1.8 server as it benefits from some of the fixes and improvements that have happened in the 2.4 stream. As long as you have not manually customized your server configuration or added in custom Apache modules, this will be just as smooth as any other upgrade to Subversion Edge. If you did customize your configuration you will need to to reapply those configurations after you upgrade. Apache 2.4 is not fully compatible with the configuration for 2.2 as it removes some directives and adds some new ones.
For existing Subversion Edge users, upgrade is a simple one-click process that you can do via the web UI. There are also instructions for doing a manual upgrade using the latest installer. For other Subversion users, now would be a good time to switch to using Subversion Edge. The migration path is relatively easy and well documented here.
We really focused this release on the upgrades to Subversion and Apache and giving users the best out of the box server configuration possible. For example, with the move to Apache 2.4 we can now safely turn on mod_deflate. This has been shown to have very positive effects on the performance of the new SVN 1.8 HTTP library used in the client. Speaking of which, the new HTTP library works differently than the old library when doing commands like checkout and update. Rather than send a single request for the content where the server has to spool back a single large response, it instead generates many smaller HTTP requests. This allows the server to be more responsive and use its resources better but a side effect is that your server access logs will grow faster. In this release we put a lot of focus on the logging configuration. You can now rotate logs by both date and size and you can also disable access logging entirely. We also added an option to suppress the logging of some of the new requests generated by the client. These are mostly internal requests that you do not need to see in order to get a good picture of what the client is doing, and it really reduces the size of the logs.
Another significant new feature is a new Advanced Settings page that gives you access to many configuration options people have asked for over the years. We try hard to make Subversion Edge as easy to use as possible which means we have to make decisions on proper defaults and try to hide those from you as much as possible. With this new release we are exposing some of those options on a separate configuration page. The vast majority of users can run their server without ever needing to even look at this page, but for that small percentage of users that need to customize a behavior this saves you from needing to manually customize the server configuration. You can now do it from the Edge web UI and we will write it to the configuration for you. Going forward, this gives us a place in the UI where we can add more of these options as needed. For now, we have exposed the settings we have been asked about the most or wanted to tweak on our own servers.
Subversion 1.8 is fully compatible with all Subversion clients. You do not have to upgrade your server and client at the same time. The 1.8 server will work with any previous version of a Subversion client, and the 1.8 client will work with any previous version of a server. Likewise, you do not have to do anything to your existing repositories. The new server can continue to serve those repositories to clients as is without anything being done. That said, there are several improvements in 1.8 in how the data in your repository is stored. If you are interested in having your repository require less disk space, then you can schedule a convenient time to dump and load your repository into a new repository created with SVN 1.8. I would not recommend doing this on day one. Go ahead and upgrade the server first and use it for a while. You can always dump and load the repositories later.
- Download Subversion Edge 4.0
- Subversion Edge 4.0 Release Notes
- Subversion 1.8 Release Notes
- Apache 2.4 New Features
* Apache, Apache Subversion and the Subversion logo are trademarks of the Apache Software Foundation. Subversion® is a registered trademark of the Apache Software Foundation.