This is working as expected in the system, although is a bit confusing. Some information is in the documentation:
https://docs.rws.com/806356/578952/sdl-tridion-docs-14-sp3/updating-a-released-topic
where this explains it as:
"Create a new branch? If you are checking out a version 1 released topic, choosing this option will branch the version. This creates a version 1.1.1 of the topic and open it in your XML editor. Any change you make then will be saved in a version 1.1.1 of the topic and leave the old content untouched in the version 1. You are still able to create a verison 2 of the topic later on."
This doesn't really explain it in too much detail - but this may help:
1. The branch and version logic is hard to grasp: V1 (version).1 (branch).1(version).1(branch).1(version), so this means you will have a prime version, then a branch value and then a version of this branch.
2. When a topic has a branch - 1.1.1 and the user wants to make a new version, a new version - 1.1.2 will be created. So this will then be 1 (Prime version) . 1 (Branch) . 2 (Branch 1 version).
Once a branch has been created, there isn't way to merge this to other branches to create a new branch. The only way to do this would be to create a new version/branch at that level and using 3rd party tools like WinMerge to merge the two branches you wish to join, being able to choose which content from which versions to include in the new version/branch of the XML. |
