BPM'Online branching strategy with SVN
We have a use-case where we have to support parallel development and UAT activities on BPM'Online. Ideally, we'd like to achieve it through a branching strategy on SVN, where we have a "main" branch for development and a "UAT" branch which is forked out of "main". This "UAT" branch will run independently of "main" to cater to UAT fixes. Once UAT is done it will be merged back with "main". During the UAT phase, the "main" branch will continue to get updated with ongoing development activities. I wanted to check if this is feasible from a BPM'Online perspective. Can this branching strategy be seemlessly integrated into BPM'Online? If yes, could you point me to some documentation that has guidelines around this?