Label all versions used in key configurations

To identify which versions of which elements contributed to a particular baseline or release, you can attach labels to these versions. For example, after Release 2 is built and tested, you can create label type REL2, using the mklbtype command. You can then attach REL2 as a version label to the appropriate source versions, using the mklabel command.

Which are the appropriate versions? If Release 2 was built from the bottom up in a particular view, you can use the following commands to label the versions selected by that view:

cleartool mklbtype –c "Release 2.0 sources" REL2
cleartool mklabel –recurse REL2 top-level-directory

Alternatively, you can use the configuration records of the release derived objects to control the labeling process:

clearmake vega

Sometime later, after QA approves the build:

cleartool mklabel –config vega@@17-Jun.18:05 REL2

Using configuration records to attach version labels ensures accurate and complete labeling, even if developers have created new versions since the release build. Development work can continue while quality assurance and release procedures are performed.

To prevent version label REL2 from being used again, you must lock the label type:

cleartool lock –nusers vobadm lbtype:REL2 

The object is locked to all users except those specified with the –nusers option, in this case, vobadm.