Version management
Version management in Tridion Docs helps you to effectively manage the content life cycle. When you need to maintain a snapshot in time of the object while continuing to make additional changes, you can explicitly create new version or branch of the object. Incremental revisions track changes between versions.
Versions
A version is a specific iteration of an object (such as a topic, map, or image). In general, you create new versions when you need to maintain the old content for publishing, such as to for older product versions that are still supported and maintained. When an object has a "Released" status, you are required to create a new version before you can make further modifications.
Branches
In addition to linear version numbering, you can branch objects from the main version tree. For example, if someone finds errors in a publication that has already been released, you can branch it and correct the branch. This allows users to continue working on the latest version of the topic while you make corrections to the older, branched content.
Revisions
A revision represents a snapshot of an object as its content changes between versions, and help to track content changes over time. .
To view revision history and perform revision rollbacks, you must use Organize Space. You can view in the history which author was responsible for a particular change, and you can restore or revert to a previous revision when needed.
Baselines
A Baseline is an object in the repository that lists the specific versions of the maps, topics, images, and library topics used in a specific version of a publication.The baseline identifies all objects in the publication by their GUID and version. A publication always contains one baseline and the baseline is specific to a publication version.
Because the baseline is specific to a publication version, you can always know which version of an object has been used in past publication versions. The following diagram illustrates how different object versions are used in different publications:
Publication versions do not have to match the versions of the objects they reference. For example, you can have version 3 of a publication that references topic and map objects with version numbers that span from 1 to 6.
To select and keep track of which versions (and branches) of objects are used in which publication versions, you must use Publication Manager to update the individual publication baselines. For example, if you create a new version of a topic that is used across multiple publication versions, and you want that new topic version to be used in several of the publication versions, then you need to individually open the each publication version in Publication Manager and select the new topic version in the baseline.