You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@curator.apache.org by Jordan Zimmerman <jo...@jordanzimmerman.com> on 2015/01/13 00:21:39 UTC
2.7.1?
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
Re: 2.7.1?
Posted by Mike Drob <ma...@cloudera.com>.
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 <mc...@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 <
> jordan@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 (madrob@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 <
> > jordan@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
> > >
> > >
> > >
> >
>
Re: 2.7.1?
Posted by Cameron McKenzie <mc...@gmail.com>.
Fine by me, thanks Jordan.
On Tue, Jan 13, 2015 at 1:30 PM, Jordan Zimmerman <
jordan@jordanzimmerman.com> wrote:
> 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.cam@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 <
> jordan@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.cam@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 <
>> jordan@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 (madrob@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 <
>> > jordan@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
>> > >
>> > >
>> > >
>> >
>>
>>
>
Re: 2.7.1?
Posted by Jordan Zimmerman <jo...@jordanzimmerman.com>.
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.cam@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 <jo...@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.cam@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 <
jordan@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 (madrob@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 <
> jordan@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
> >
> >
> >
>
Re: 2.7.1?
Posted by Cameron McKenzie <mc...@gmail.com>.
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 <
jordan@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.cam@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 <
> jordan@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 (madrob@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 <
> > jordan@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
> > >
> > >
> > >
> >
>
>
Re: 2.7.1?
Posted by Jordan Zimmerman <jo...@jordanzimmerman.com>.
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.cam@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 <
jordan@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 (madrob@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 <
> jordan@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
> >
> >
> >
>
Re: 2.7.1?
Posted by Cameron McKenzie <mc...@gmail.com>.
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 <
jordan@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 (madrob@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 <
> jordan@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
> >
> >
> >
>
Re: 2.7.1?
Posted by Jordan Zimmerman <jo...@jordanzimmerman.com>.
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 (madrob@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 <
jordan@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
>
>
>
Re: 2.7.1?
Posted by Mike Drob <ma...@cloudera.com>.
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 <
jordan@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
>
>
>