Let say for first after install bug fix set of files {A', B', C'} was changed.
To deliver it we should deploy on customer's system all this new files together
at once, but only if old files were present.
Now what about next fix?
Let assume change set for it is {D', E', F'}. It may happen that this change
may work as expected without first change in files {A', B', C'}. This two
changes may be independent. However some file like E' may have new
functionality which were not present before and which relays on changed file A'
for example. In this case second change will not work without first one because
E' require A' and because change must be delivered all at once or nothing {D',
E', F'} require {A', B', C'} be present on the customer's computer. This is
another type of dependency - it is only one-way dependency between changes.
This dependency developer may expect because what is changed is known, or it
may be found during testing of second change without first change.
Now let say second change set is {C'', D', E', F'}. In this case second set
contain new version of C - C''. C'' has new changes as well as old changes from
first fix C'. In this case by delivering C'' we as well delivering C' an if we
deliver C' then A' and B' also need to be delivered! In this case second change
for sure 100% depends on first change - no need to do testing or analysis.
This message posted from opensolaris.org
