Branch Based Rules in Config Specs

This is in the context of (base) ClearCase, and more specifically of branch uses.

One can specify element * .../some_branch/LATEST (with a -mkbranch branch clause), but this brings some shortcomings:

• the same as with labels, because of a dependency on the order of rules, in case they conflict with each other;
• the fact that the owner of some_branch might chtype her branch away e.g. after labeling it (for publication to some degree), which one won't catch until after a setcs -current which reevaluates the mapping of the branch type name.
• and of course, what one sees as LATEST from some_branch may or may not, for different reasons, be consistent, which leads to further discussions. Checking in intermediate results should always be allowed. Why this would create a problem in this case is the consequence of an unfortunate coupling between checkin and publication.

-- MarcGirod - 03 Oct 2007