Making a new descendant baseline
Making a new descendant for a pure composite baseline indicates that the relationship between member baselines has changed. The loosely coupled relationship in a pure composite baseline indicates that the project integrator manages the dependency among the components outside of the DevOps Code ClearCase® environment. This form of dependence provides more choices of baselines to use in a project. Because the dependency relationship does not enforce the changing of component A if component C changes, the project integrator must be more careful in selecting baselines but has more flexibility in making changes.
Making a new descendant for a composite baseline of an ordinary component
when the predecessor baseline changes can indicate one or both of the following
meanings:
- Changes in the baseline dependency relationships
- Changes in the elements that make up the components
In a tightly coupled dependence, a change in component C enforces changing component A.