On 01/08/2016 05:15 PM, Eike
I may misunderstand this fixed
version stuff, so I better ask explicitely. I will not be
forced to author exact feature versions in my contribution
I'm fine with the rule of contributing only fixed content,
but I prefer to achieve that goal with non-changing repos.
The rule currently accepts version ranges with "changing"
repository URL. However, it seems very difficult to write
good tests that guarantee that the rule is respected...
That's why I'm trying to push towards the 4-digits version
rule as "de-facto standard", since it can trivially be
>From your contributor point-of-view, what makes changing
the version more difficult that changing an URL? In any
case, you'll have to make a change in the b3aggrcon file
whenever you want to contribute something new. It seems to
me that the extra-cost of changing the version when also
changing the URL is not that high, is it?