So, you’ve bought Unity Pro and the Unity Asset server. If you’re like me, in spite of its disadvantages, you really like the UAS. It’s integrated into the editor and does a much cleaner job of versioning on serialized assets than does external version control, because it operates on the project’s Library folder rather than requiring you to generate and synchronize all of the sidecar data. However, there are some key things it cannot do.
I don’t have very complicated needs like branching and so on, but I do have a library of common code that I share across projects. This library contains a bunch of useful stuff that doesn’t rely on any game systems: things like helper classes, math classes, serialization for built-in types, and so on. The trouble is, I’m often working simultaneously on a bunch of projects that share my library (or worse still parts of my library), and so it can be a pain in the neck to push the changes out across all my projects. As such, I took the time to set up a system using Subversion working on top of my UAS projects in order to synchronize my library code.