Integration of configuration management (CM) tools into software development environments raises the need for CM models to interoperate through a unified CM model. A possible foundation is the version set model, a unified model for specifying versions and version operations, where versions, components, and aggregates are grouped into sets according to their features, using$eature logic as a formal base to denote sets and operations and deduce consistency. Version sets generalize well-known CM concepts such as components, repositories, workspaces, aggregates, or configurations and allow for unprecedented flexibility in combining these concepts, Arbitrary revisionhwiant combinations of components and aggregates are modeled in a uniform and orthogonal way. We show how the concepts of four central configuration management models-the checlchdcheckout model, the change set model, the composition model, and the long transaction model-are encompassed and combined
No takes yet. Share an insight, caveat, or question.
Andreas Zeller (1995) studied this question.
Synapse has enriched 5 closely related papers on similar clinical questions. Consider them for comparative context: