Version management
When you check in a topic, library topic, map, or image to the repository, SDL LiveContent Architect automatically creates a new revision of the object but not a new version. When needed, you must explicitly create new versions of an object .
Revisions
You can view an audit trail to see which author was responsible for a particular change, and you can restore or revert to a previous revision when needed.
Versions
All versions of an object are stored under the same object ID (GUID), and each version has a unique version number. Because you may create a new version number at any time, it is important to provide guidance identifying when it is necessary or appropriate to create a new version of an object. For example, teams with an iterative development cycle, such as an Agile cycle, may want to create a new version at the end of each iteration.
You can specify versions for publication objects. Publication object versions do not have to match the versions of the objects they reference. For example, you can have version 3 of a publication object that references objects with version numbers that span from version 1 to version 6. Users are responsible for specifying the proper versions of objects to include in specific versions of a publication object.
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 be 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. A branch can easily be recognized since the version number of a branch follows a specific numbering mechanism.
Baselines
A baseline lists the specific versions of the maps, topics, images, and library topics used in a publication. The baseline object is always preserved so that it is possible to determine the version of the object that was used for a publication.