CollabNet Subversion Edge Shines with Solaris

I am pleased to announce the immediate availability of CollabNet Subversion Edge 1.3.0. The defining feature of this release is support for Solaris 10 on sparc and x86. With this release we now are providing Subversion Edge on all of the same platforms as our original CollabNet Subversion binaries. Of course we have actually expanded the number of platforms as we also officially added support for SuSE 11, Windows Vista/7 and 2008 Server, not to mention 64-bit Windows.

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 …

Read More »

Building an OS X based Subversion Server

This article explains in-depth how to build a Subversion server on OS X.

Mirror Management: How Often Should I Sync?

You’ve setup Subversion mirrors. How often should should you mirror? Should you synchronize often with a smaller number of changes, or only once in a while with larger amount? Subversion committer C. Michael Pilato gives his view.

Considerations when upgrading to Subversion 1.5

Upgrade considerations for Subversion 1.5

Subversion 1.4.5 Released

Subversion 1.4.5 was released today. The only change from Subversion 1.4.4 is a patch for a Windows client security exploit.

Single Repository or Many?

My previous blog entry discussed the issue of repository layout. This entry will try to answer the question of whether you should have one repository per project or a single repository that houses all your projects. There is not going to be a single right answer to this question. Hopefully this post will help you understand the tradeoffs so you can make the right decision that suits your requirements. These are some of the advantages of the single repository approach. 1. Simplified administration. One set of hooks to deploy. One repository to backup. etc. 2. Branch/tag flexibility. With the code …

Read More »

Subversion Repository Layout

I see a lot of questions asked about “What is the recommended repository layout?”, “What does trunk mean?”, or: “What is the significance of trunk?”. This post will try to answer those questions and more. A Subversion repository implements the metaphor of a versioned filesystem. The repository is just a filesystem with folders and files. It so happens that modifications to this filesystem are versioned and there are implementation enhancements like “cheap” copies that make certain operations less expensive than they are in a traditional filesystem, but the repository itself still behaves like a filesystem: there are no special folders …

Read More »

Subversion LDAP Authentication with Apache

This blog entry is now obsolete.  A newer, more in-depth version is   available here: Subversion with   Apache and LDAP: Updated More and more companies are using directory services for housing their user credentials and information.  Example directory services are Active Directory, eDirectory and OpenLDAP.  How does this relate to Subversion?  Well, in the enterprise deployments I’ve been involved with, most clients wanted to harness their existing directory services for their Subversion authentication.  This blog post will explain the simplicity of hooking up Apache to your directory service using mod_auth_ldap, giving you the ability to authenticate against your existing …

Read More »