Version policy : third-party upgrades in a minor release ?

[Tom Zeller]

> On Oct 24, 2015, at 5:45 AM, Rod Widdowson <rdw at steadingsoftware.com> wrote:
> 
>> I used this :http://ispras.linuxbase.org/index.php/Java_API_Compliance_Checker
> ? To generate this: https://issues.shibboleth.net/jira/secure/attachment/11830/compat_report.html
> 
> Very cute!
> 
>> I found it very useful, but you still need a human to analyze it.
> 
> And preferably someone with a good knowledge of either the library under investigation of an in depth knowledge of our uses of them.
> 
> OTOH it appears to me that just by skimming the report one can get a feel for how well behaved the developers have been with respect to our rules which can always help our value judgement about our ongoing trust of that project’s version policies…

Some more data points :

./japi-compliance-checker.pl $path/ldaptive-1.0.6.jar $path/ldaptive-1.0.7.jar
result: COMPATIBLE

./japi-compliance-checker.pl $path/ldaptive-1.0.6.jar $path/ldaptive-1.1.0.jar
result: INCOMPATIBLE (Binary: 2.8%, Source: 6.4%)

./japi-compliance-checker.pl $path/ldaptive-1.0.7.jar $path/ldaptive-1.1.0.jar
result: INCOMPATIBLE (Binary: 2.8%, Source: 6.4%)

./japi-compliance-checker.pl -lib spring-framework spring-framework-4.2.1.xml spring-framework-4.2.2.xml
result: COMPATIBLE

./japi-compliance-checker.pl -lib spring-framework spring-framework-4.1.5.xml spring-framework-4.2.2.xml
result: INCOMPATIBLE (Binary: 1.7%, Source: 3.6%)

where, for example, spring-framework-4.1.5.xml :

<version>
    4.1.5.RELEASE
</version>

<archives>
    $path/org/springframework/spring-aop/4.1.5.RELEASE/spring-aop-4.1.5.RELEASE.jar
    $path/org/springframework/spring-beans/4.1.5.RELEASE/spring-beans-4.1.5.RELEASE.jar
    ...
</archives>

And finally the question that kinda started it all :

./japi-compliance-checker.pl $path/jcommander-1.47.jar $path/jcommander-1.48.jar
result: COMPATIBLE

So, I think it’s okay to bump jcommander in the next IdP minor release.