Footnotes

 

(1)

University of Bremen  

(2)

People who doubt the necessity of alpha versions of specifications should note that during the implementation process, usually specifications are not static, but rather specifications and implementations are debugged against each other. [Pnu98]  

(3)

Version management systems often contain a merge tool that can merge 1.5.4 with 1.6.2 if the latest common ancestor (here: 1.5.3) is provided. Typically, about 80% of the merging can be done automatically, 20% have to be done by hand.  

(4)

More precisely, by an explicit reference to the latest version number that is valid for the considered library, instead of using the default mechanism. This is important in order to get a static version just after the rejuvenation. It is enough work to get this new static version consistent. Working with a possibly changing, dynamic version is unrealistic.