Subversion Edge 2.2 was released this week and brings some exciting new features that our users have been asking for. A general changelog for the release can be found in the wiki. Here are some of the highlights:
The Apache Subversion binaries have been updated to the latest release. Subversion 1.7.2 is a bug fix release, the changelog can be found here.
Prior to this release when creating a new repository your choices were to create an empty repository or to initialize it with the standard trunk/branches/tags structure. A number of users requested the ability to initialize repositories with the standard folder structure that they use in their organization, and other users have asked for the ability to install their standard hook scripts. This release introduces the concept of repository templates which provides both of these features. A repository template can either be a standard Subversion dump file or a zipped copy of a Subversion repository. In either case, the repository can contain whatever content you want and in the case of a zipped repository the template can also include hook scripts.
With this feature you could now disable our templates and replace them with your own that include things like your standard hook scripts and/or the default repository structure that you want. Technically, the template repository can include as much content as you desire, so if you have some standard document or project templates that content can also be included in the repository template.
New Create Repository UI
To go with the previous feature, and to add another one, we have revamped the Create Repository UI. When creating a repository you now have the option of initializing the repository from a template OR from a backup. This works in conjunction with the backup feature we added in the 2.1.0 release by providing a UI to restore any of those backups as part of creating your repository.
REST API – CollabNet Desktop Support
We are in the process of exposing the Subversion Edge administration capabilities via REST API. This release brings the initial release of some of that API. For this release, we focused on the API needed to address the user stories for our CollabNet Desktops. Prior to this release, the desktops only supported Subversion Edge via their capability of working with any Subversion repository. With this release, the desktops now have first class support for Subversion Edge. You can add a Subversion Edge “site” in the desktop by providing the URL and credentials for your Subversion Edge console. The desktop can then use the new REST API to retrieve the list of repositories available and make then instantly accessible in your client. If you work with multiple Subversion repositories this saves you from having to manage connections to each repository. Just connect your client to Subversion Edge and any repositories are instantly available in your client.
The Eclipse Desktop also has support for the Subversion Edge Discovery API. If your client is located on the same LAN segment as the Subversion Edge console you can click a Browse button and have your Subversion Edge server(s) discovered automatically. You still need to provide valid credentials to access the console, but this makes it easy to find it and add the correct URL.
Proxy Server Support
Many users install Subversion Edge on servers that are behind a corporate proxy. When Subversion Edge needs access to the Internet, such as to check for updates or to act as a replica for TeamForge, the proxy server needs to be configurable. Prior to this release you had to configure proxies manually by editing environment variables and configuration files. We have now pulled this into the Subversion Edge UI so you can easily configure your proxy server from the web interface.
This is our 15th release of Subversion Edge since introducing it in the summer of 2010 and there will be more releases to come in the next year. On behalf of the Subversion Edge team I want to thank you for your tremendous support for this product. Happy Holidays! We will see you next year!