Not sure. It compares two JARs, so we'd need to have (or build) the previous release in order to have something to compare against. For automation through maven, we might consider looking at the Clirr plugin[1].
Probably want to take further discussion to a JIRA issue so as not to de-rail the release discussion any further. [1]: http://mojo.codehaus.org/clirr-maven-plugin/usage.html On Mon, Jan 12, 2015 at 4:07 PM, Cameron McKenzie <[email protected]> wrote: > I agree that this should be a 2.7.1 release. > > Cool tool Mike, would it be easy to create a maven task to run it? > > On Tue, Jan 13, 2015 at 10:51 AM, Jordan Zimmerman < > [email protected]> wrote: > > > Wow - that’s a cool tool. I didn’t know about it. The constructor change > > won’t affect any clients as it’s not meant to be used directly. > > > > > > > > On January 12, 2015 at 6:48:32 PM, Mike Drob ([email protected]) > wrote: > > > > I ran the japi-compatability-checker tool[1] to verify, and this was the > > only issue that it found[2]. I think that's enough to push us into a > minor > > release over a bugfix according to SemVer rule #7, but I'm not 100% sure. > > > > [1]: http://ispras.linuxbase.org/index.php/Java_API_Compliance_Checker > > [2]: http://people.apache.org/~mdrob/curator-2.7.1/compat_report.html > > > > On Mon, Jan 12, 2015 at 3:21 PM, Jordan Zimmerman < > > [email protected]> wrote: > > > > > I think we have a good set of fixes for 2.7.1. Thoughts? Also, I don’t > > > think these merit 2.8.0. > > > > > > > > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314425&version=12328938 > > > > > > -Jordan > > > > > > > > > > > >
