commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Siegfried Goeschl <>
Subject When to create a new major release - Was [VOTE][CANCEL] The vote for commons-email-1.3 based on RC2 in cancelled
Date Tue, 10 Jan 2012 16:45:40 GMT
Hi folks,

the main reason for the failed vote of commons-email-1.3 is that the 
release is only source but not binary compatible

+) if you compile your application with the new version everything is fine
+) if you replace simply the JAR the invocation fails

Is it mandatory that a minor release is binary compatible with the 
previous one or do I have to create a new major version? There is a lot 
of ugly stuff (mainly protected member variables) which should be done 
but is currently not in the scope of this release.

Feedback appreciated

Siegfried Goeschl

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message