Transitioning from Rational ClearCase to UCM

Slides

old in-house tracking tools: shell scripts

maintenance problems, staff busy, limitations (Unix, inefficiencies)

chasticizing wrappers, state-transitions and attributes

e.g.: one branch per project, directories not versioned

shortcuts. e.g. start new projects instead of new branches

UCM: way out past errors

Couldn't find expertise

defect model too simple

MultiSite process despite the intention

CQ not happy with loops in the normal flow (reporting clumsy etc...)

Inflexible components

Changed mind on read-only components

Conflicts with all practices

rebase requires checking in

import to a non-ucm branch, label and set the integration stream to use
this label. The stream is thus a logical branch.

heavy process to revert to a previous baseline, loss of changes

problem was modification between delivery and baseline

answer: lock of integration stream. Prevents join project

single integrator

pull - multiple deliveries: the order cannot be changed afterwards

No partial delivery

No changes (even temporary) in read-only components

rebase and delivery: new activity union of other activities

Failed integration because of access rights

New integration resulted in duplicated activities

RUC 2001 ToC
Marc Girod
Last modified: Fri May 14 09:57:44 EEST 2004