Recommended SVN branching strategy for DevOps
We use Git for our VCS. We follow Trunk based development strategy.
Trunk-Based Development (TBD) is where all developers (for a particular deployable unit) commit to one shared branch under source-control. That branch is going to be colloquially known as trunk, perhaps even named “trunk”. 
 lie of omission

This trunk is always stable, but it can have unfinished features covered by feature toggles. This type of development works 


When you are just starting up 
When you are iterating quickly


In short, feature branches will give you better isolation, but require you to deal with the pain of deferred integration, and merges. Toggles give you continuous integration, but require you to design/implement your code in such a way that supports toggles, and introduce the risk that unfinished feature code could negatively affect production.