Scenario 4 - Base-lining a project
Return to Introduction  Previous page  Next page
Many users are now using GP-Install and, although it is free, it has been decided that each new release will be marked with a different Version Label. In addition, a tailored version is now being sold to several customers. Development of the free version has been stopped, apart from bug fixes, while the current release is still under development.

Joanne has made the changes for the commercial version to a local copy of the code, but has not checked her changes back in yet. The current archived code is still the code used in the free product. Before checking in the code for the commercial version, she decides that it would be a good idea to mark the current free version code with a Version Label to distinguish it from the commercial version.

She decides that the existing, free, code should be marked with the LITE version label. She selects the GP-Install project in Version Manager and selects Action/Version Label… from the main menu. The Version Label dialog box is displayed. She is creating a new label so she presses the ellipsis (...) next to the Version field and creates a new Version Label. This label is automatically selected in the Version Label dialog box and, when she presses the OK button, Team Coherence attaches the LITE Version Label to the latest (tip) revision of all the files in the GP-Install project. Once it is complete, the status dialog is displayed.

Joanne's heart sinks. She realizes that she has already checked in one of the files, and it contains code specific to the commercial release. The file is InstGlobal.pas and contains code that would add too much extra functionality to the LITE version. She knows that she has been the only one working on the commercial release of GP-Install so decides to move the Version Label that has been attached to the InstGlobal.pas file back to the revision that should be included in the LITE version.

She selects the InstGlobal.pas file in the File pane to display its revisions in the Detail pane and sees that the tip revision has been marked with the version label. She is pretty sure that the previous revision is the one that should have the label attached to it so she selects the previous revision and uses the difference viewer to verify that the changes are in the tip revision. Satisfied, she selects the revision with the LITE version label and selects Action/Remove Version Label… from the main menu and enters LITE in the version edit box. She notices that the description for that label is displayed in the Comments box, and presses OK to remove the label.

The label is removed OK, so she selects the revision that the label should have been attached to and selects Action/Version Label… from the main menu. The Version Label dialog box is displayed and she selects LITE from the Version Label drop down list. When she presses the OK button, Team Coherence attaches the Version Label to the selected revision.

Happy, now that the LITE version has been correctly versioned, she checks in the commercial version.

 


© 1995-2018 MCN Software