There’s “demand” so I’ll start it now - barring any objections. -JZ
On January 12, 2015 at 9:29:55 PM, Cameron McKenzie (mckenzie....@gmail.com) wrote: I can do it next week if we can wait until then, I'm away from home until next week so I'm a bit limited in what I can do. cheers On Tue, Jan 13, 2015 at 1:14 PM, Jordan Zimmerman <jor...@jordanzimmerman.com> wrote: Anyone else want to do the release? Otherwise, I can start it. -Jordan On January 12, 2015 at 7:07:31 PM, Cameron McKenzie (mckenzie....@gmail.com) 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 < jor...@jordanzimmerman.com> 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 (mad...@cloudera.com) 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 < > jor...@jordanzimmerman.com> 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 > > > > > > >
