This post is from the CollabNet VersionOne blog and has not been updated since the original publish date.
CollabNet Subversion Edge 1.2 Released
CollabNet Subversion Edge 1.2 has been released today, an overview of the new features is available on the project home page. It is also worth noting that we have mostly completed the transition of the project from our internal TeamForge instance, where it was originally developed, to a fully open-source project hosted on openCollabNet. The source code repository, issue tracker, wiki and discussions are now all on openCollabNet and are being actively used for all development. The only remaining work is to provide publicly accessible replacements for some of our internal build systems and also some remaining migration of the tracker artifacts that are still open in our internal trackers.
The primary new feature in Subversion Edge 1.2 was to add support for converting a Subversion Edge server running on Windows so that it can be managed by TeamForge. The 1.1 release added this feature for Linux and this release adds the same for Windows. Converting a Subversion Edge server to TeamForge mode provides additional functionality that you get from using TeamForge. You get immediate access to the role-based access control functionalities of TeamForge and the ability to delegate administration functions to project managers. Of course you also have the option of using all of the ALM features provided by TeamForge such as trackers and dynamic planning. If you want to get an idea what TeamForge can provide for you, take a look at our project for Subversion Edge. We are using the TeamForge agile ALM capabilities to manage our agile scrum process for developing Subversion Edge.
The other major change we added in this release was to ship the Subversion Edge console so that it was pre-configured to run with SSL using a self-signed certificate. When the Subversion Edge console starts it will listen with plain HTTP on port 3343 and HTTPS on port 4434. You can connect to the server using either port depending on whether you want to use SSL or not. There is also a new setting on the Administration tab to “require SSL”. If you check this box, then attempts to access the server on port 3343 will be redirected to port 4434. If you had previously manually configured Subversion Edge to use SSL your configuration will be replaced with this new configuration. You can put your configuration back or you can change the new configuration to point to the Java keystore that contains the certificate you want to use. Speaking of which, it is still a good idea to replace our self-signed certificate with an official SSL certificate that you purchase from a trusted certificate authority. If you do not do this, then your users will need to accept the certificate warnings in their browser. There is some information on configuring the SSL connection in the wiki.
As always, please provide us feedback and ask questions on using Subversion Edge in our discussion forum.
* Apache, Apache Subversion and the Subversion logo are trademarks of the Apache Software Foundation. Subversion® is a registered trademark of the Apache Software Foundation.