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: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Reply via email to