[daniel-levin]

I'm going to answer the question, rather than tell OP they should just use git.

It might be worthwhile to check out Perforce [1]. Downsides: proprietary, expensive. Upside: you can version all sorts of content at a high level, not just software. I know of a large embedded shop that swears by Perforce.

[1] https://www.perforce.com/solutions/version-control

[zbuf]

I did consider that in my reply. But then the poster is really getting to grips with branching, and so I didn't feel the tool was the weakness here.

However, it's worth considering if subversion is actually what you need (I haven't used Perforce but I have heard its underlying structure is conceptually similar?) I saw sysadmins struggling with Git when all they needed was to enforce good use of a single branch, and central repository and some history. They felt they should be using Git, and in doing so threw away a tool that was already a good match to their workflow.

[michaelmrose]

User would still be stuck learning git in order to contribute to almost anything or for the majority of jobs. It might make sense to learn in addition to git I'm not sure its as good an idea instead of.