On Wed, 23 Oct 2002 goran.hultgren@bluefish.se wrote:
If I didn't introduce that term it means more or less that if a package A is dependent on version 1.22 of B then if B moves to 1.25 by 3 update ChangeSets all classified as "no behaviour change" then we can be sure that A will work with B 1.25 too. And if say the last one is classified as "should be backwards compatible" we can still be pretty safe, etc. So, the dependency can "stretch".
Can't this be done more simply by using a major.minor.patch convention for version numbers? You could have a dependency on 1.2, which would accept 1.2.0, 1.2.2, 1.2.5, etc...