Chapter 9 Managing Document Versions in the Repository
A configuration is a set of document versions created to formalize the links between document versions. A configuration labels document versions in the repository in order to recover them easily.
Unlike branches, configurations cannot be empty, you create a configuration by inserting document versions in it. You cannot create configurations when you do not have any document version consolidated in the repository.
We will use the same example of a development team working on a software project. During the development of the software, it is useful to label the versions used for a major or minor release. You can use the configuration feature to link document versions.
Usually, the team leader has the right to manage configurations in the repository. In our example, versions used for a minor release are circled, they are included in the same configuration called Minor Release:
Configurations are very useful when you need to extract documents.
In this example, when an engineer has to correct bugs on the minor release for the first time, he needs to have the appropriate versions of the documents on his local machine to start working:
He can select one of the model versions used for the release and add the other versions of the configuration to the extraction list. After extraction, he has the correct work environment to start correcting bugs, he no longer needs to extract the configuration.
| Copyright (C) 2006. Sybase Inc. All rights reserved. |
| |