Version control
Version control provides team members with three constructs to manage changes to software components:
•Editions
•Versions
•Scratch editions
These constructs help the team to achieve two goals that are desirable in a team programming environment:
1. Flexibility is achieved, because software components can be developed along alternate paths. These paths can be specific to one image, or can be shared among images.
2. Stability is achieved, because versions create an immutable baseline of components that developers can share.
Editions and versions also allow developers to reload a previous version of their work. The capability to load previous versions is desirable in the case that, for example, work on the current edition of a component reaches a dead end.
Last modified date: 01/29/2015