[Zope-dev] Why several versions in controlled-packages.cfg?

[Christophe Combelles]

I'm wondering why there are several versions of packages in 
controlled-packages.cfg? Isn't the KGS supposed to point to a fixed set of 
unique versions ?

I'm asking because I think it's completely impossible to test every combination 
of packages:

Imagine the controlled-packages.cfg is

zope.foobar: 3.4.0
              3.4.1
zope.baz: 3.4.0
           3.4.1
           3.4.2
zope.blah: 3.5.4
            3.5.5

Suppose you want to add the bugfix release zope.foobar 3.4.2 into the KGS. When 
you launch the full test suite of the KGS, you are actually testing zope.foobar 
against all the latest versions, not ALL the versions. If zope.foobar 3.4.2 is 
not compatible with zope.baz 3.4.0, you won't see it, unless you launch the test 
for every combination of packages:
zope.foobar: 3.4.2  + zope.baz: 3.4.0 + zope.blah: 3.5.4
zope.foobar: 3.4.2  + zope.baz: 3.4.0 + zope.blah: 3.5.5
zope.foobar: 3.4.2  + zope.baz: 3.4.1 + zope.blah: 3.5.4
zope.foobar: 3.4.2  + zope.baz: 3.4.1 + zope.blah: 3.5.5
zope.foobar: 3.4.2  + zope.baz: 3.4.2 + zope.blah: 3.5.4
zope.foobar: 3.4.2  + zope.baz: 3.4.2 + zope.blah: 3.5.5

In the real world, there are a lot more packages (but ok, every package is not 
dependent of every other). So the controlled-packages is impossible to test. The 
real KGS is the set of latest versions. Why shouldn't we put only the latest 
versions in controlled-packages ?

Christophe