Ericsson RSA/P Best Practice

1.5 REVISION CONTROL STEP-BY-STEP

One of StarTeam’s most important features is revision control. StarTeam supports a variety of labeling methods for revision control: view-, build- and revision-labels.

Every time a file is checked in, StarTeam updates the internal revision information for that file. The Labels tab provides the connection between internal revisions and labels. Internal revisions is displayed in the format 1.1, 1.2 etc, while labels should be used to specify the Ericsson revision (R1B etc).

1.5.1 Using View Labels

The correct way to use StarTeam in the RSA/P software environment is to use View Labels to manage revisions.

Since all types of labels only appear in the view they were created, it is imperative that all work on a project or test-program is done in the appropriate view (for example the CAL 120 352.-1 or Nexus view).

1.5.2 Attaching a new View label

View labels are attached by selecting the Labels option from the View menu. The most common practice is to attach a new view label when a major milestone is passed. For example the test-program is promoted from R1F to R1G.

Make sure the Current configuration option is marked if you wish to attach the labels to the newest (current) version of the files.

View labels can be moved as long as they are not frozen. Moving a label is done by usage of the drag-and-drop method in the labels tab (lower right pane in StarTeam).

1.5.3 Branching a current or old revision

One of StarTeam’s most useful features is its ability to branch a view based on view labels. Take this example: the current revision of CAL 120 352/1 is R1F and the development department wished to add special functions to revision R1E of the same program. The changes should be made WITHOUT affecting the R1F release.

This is accomplished by creating a new view based on the view labels designated R1E. Make sure the root folder is selected (the CAL or project name). Select New.. from the View menu. Since we don’t want the changes to R1E to affect the current (R1F) revision, we select the Permit items to branch option. We also have to set the Default Item Branching to Branch All:

Click Next and give the new view the same name as the revision labels (in this example R1E). Click Next. Make sure the root folder is selected. Click Next.

This next step is important to avoid merge problems. A new local working directory must be entered. In compliance with RSA/P norms the new folder should have “_” added. In this example “_R1E”. When fully printed “C:\Projects\RSA-P-TA\Testprog\CAL120352.-1\” becomes “C:\Projects\RSA-P-TA\Testprog\CAL120352.-1_R1E”. Click Next.

In the next dialog you have to specify the view label that the new view should be based on. In this example we select R1E:

Click Next.

You are now working in a separate “R1E” view. Changes made to files here will not affect the previous view (R1B, R1F etc). You have now branched your project.

<< previous page first page next page >>

The information in this document is published with permission by Ericsson Radio Access.
is the trademark or registered trademark of Telefonaktiebolaget LM Ericsson.

Fox Data AB, P. O. Box 78, 194 22 Upplands Vasby, Sweden. Telephone +46-8-626 8100.
For general information, please send an e-mail to: Info. For sales inquiries contact: Sales. If you have questions about our web site, please contact Webmaster. Copyright Fox Data AB, 1993 - 2007.