I saw this on Dot Net Kicks today and just had to comment on it.  It is a great article about using Subversion and branching.

Branching code for features

It is almost a given in the current development world that you will be implementing new features while performing maintenance at the same time.  That makes it very hard to release a patch for a certain build without releasing new features into the wild as well.  This has been a problem for VistaDB in the past and is one high on our list of things to correct from a process standpoint.

Subversion - like it / hate it

I have a love hate relationship with Subversion.  I love the concepts and even the implementation of the server, just not the clunky clients.  Almost all of them are pathetic compared to a commercial revision control system.  I don't WANT to be forced to use it in Visual Studio, or like a File Explorer.  It is a separate app for me - and I like them to be full featured. 

The branching system is brilliant in Subversion, I wish our current system was that clean.  Although to be fair we did just upgrade to the latest Surround SCM in the past week and I have not had a chance to play with their latest effort.

I want to search for all files I have changed, or maybe that someone else on the team has changed.  I like being able to see my history information, etc.

I have seen a few decent attempts for Subversion clients, but they almost all are implemented in Java or some other cross platform system that always feels clunky and non-Windows like to me.