You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@curator.apache.org by Jordan Zimmerman <jo...@jordanzimmerman.com> on 2015/04/21 18:01:39 UTC
Curator 2.8.0 (formerly 2.7.2)
I think we have enough for a 2.8.0 release. Discuss now, please, if you’d like to see any other issues in the next release.
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314425&version=12329300
-Jordan
Re: Curator 2.8.0 (formerly 2.7.2)
Posted by Cameron McKenzie <mc...@gmail.com>.
Can one of the committers look at the fix for CURATOR-154. I setup a pull
request some time ago, pretty simple fix, just needs a quick review then I
can merge it in for this release.
cheers
On Wed, Apr 22, 2015 at 3:03 AM, Jordan Zimmerman <
jordan@jordanzimmerman.com> wrote:
> I’d like to wait on CURATOR-148 as part of larger usability pass on
> Curator.
>
> -Jordan
>
>
>
> On April 21, 2015 at 11:35:59 AM, Mike Drob (madrob@cloudera.com) wrote:
>
> Ack, I meant to say that I would like CURATOR-148 but don't know how
> compatible it is. Brain and fingers didn't agree.
>
> On Tue, Apr 21, 2015 at 9:33 AM, Jordan Zimmerman <
> jordan@jordanzimmerman.com> wrote:
>
>> I merged CURATOR-204 (apache 16 is the latest). I’ll take a look at
>> CURATOR-164 as well.
>>
>> -JZ
>>
>>
>>
>> On April 21, 2015 at 11:12:52 AM, Mike Drob (mdrob@apache.org) wrote:
>>
>> I'd like to see CURATOR-204. I'll check later today if there is an
>> apache-parent-17 that we should be using instead of 16, even.
>>
>> Maybe we can also do CURATOR-164, I'll try to finish it up this week.
>>
>> CURATOR-164 would be nice, but I'm not sure how those look from a
>> compatibility viewpoint.
>>
>> We should also pay attention to the ask in CURATOR-193 and make sure that
>> we don't run into anything similar for 2.8.0.
>>
>> Mike
>>
>> On Tue, Apr 21, 2015 at 9:01 AM, Jordan Zimmerman <
>> jordan@jordanzimmerman.com> wrote:
>>
>>> I think we have enough for a 2.8.0 release. Discuss now, please, if
>>> you’d like to see any other issues in the next release.
>>>
>>>
>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314425&version=12329300
>>>
>>> -Jordan
>>>
>>
>>
>
Re: Curator 2.8.0 (formerly 2.7.2)
Posted by Jordan Zimmerman <jo...@jordanzimmerman.com>.
I’d like to wait on CURATOR-148 as part of larger usability pass on Curator.
-Jordan
On April 21, 2015 at 11:35:59 AM, Mike Drob (madrob@cloudera.com) wrote:
Ack, I meant to say that I would like CURATOR-148 but don't know how compatible it is. Brain and fingers didn't agree.
On Tue, Apr 21, 2015 at 9:33 AM, Jordan Zimmerman <jo...@jordanzimmerman.com> wrote:
I merged CURATOR-204 (apache 16 is the latest). I’ll take a look at CURATOR-164 as well.
-JZ
On April 21, 2015 at 11:12:52 AM, Mike Drob (mdrob@apache.org) wrote:
I'd like to see CURATOR-204. I'll check later today if there is an apache-parent-17 that we should be using instead of 16, even.
Maybe we can also do CURATOR-164, I'll try to finish it up this week.
CURATOR-164 would be nice, but I'm not sure how those look from a compatibility viewpoint.
We should also pay attention to the ask in CURATOR-193 and make sure that we don't run into anything similar for 2.8.0.
Mike
On Tue, Apr 21, 2015 at 9:01 AM, Jordan Zimmerman <jo...@jordanzimmerman.com> wrote:
I think we have enough for a 2.8.0 release. Discuss now, please, if you’d like to see any other issues in the next release.
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314425&version=12329300
-Jordan
Re: Curator 2.8.0 (formerly 2.7.2)
Posted by Mike Drob <ma...@cloudera.com>.
Ack, I meant to say that I would like CURATOR-148 but don't know how
compatible it is. Brain and fingers didn't agree.
On Tue, Apr 21, 2015 at 9:33 AM, Jordan Zimmerman <
jordan@jordanzimmerman.com> wrote:
> I merged CURATOR-204 (apache 16 is the latest). I’ll take a look at
> CURATOR-164 as well.
>
> -JZ
>
>
>
> On April 21, 2015 at 11:12:52 AM, Mike Drob (mdrob@apache.org) wrote:
>
> I'd like to see CURATOR-204. I'll check later today if there is an
> apache-parent-17 that we should be using instead of 16, even.
>
> Maybe we can also do CURATOR-164, I'll try to finish it up this week.
>
> CURATOR-164 would be nice, but I'm not sure how those look from a
> compatibility viewpoint.
>
> We should also pay attention to the ask in CURATOR-193 and make sure that
> we don't run into anything similar for 2.8.0.
>
> Mike
>
> On Tue, Apr 21, 2015 at 9:01 AM, Jordan Zimmerman <
> jordan@jordanzimmerman.com> wrote:
>
>> I think we have enough for a 2.8.0 release. Discuss now, please, if
>> you’d like to see any other issues in the next release.
>>
>>
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314425&version=12329300
>>
>> -Jordan
>>
>
>
Re: Curator 2.8.0 (formerly 2.7.2)
Posted by Jordan Zimmerman <jo...@jordanzimmerman.com>.
I merged CURATOR-204 (apache 16 is the latest). I’ll take a look at CURATOR-164 as well.
-JZ
On April 21, 2015 at 11:12:52 AM, Mike Drob (mdrob@apache.org) wrote:
I'd like to see CURATOR-204. I'll check later today if there is an apache-parent-17 that we should be using instead of 16, even.
Maybe we can also do CURATOR-164, I'll try to finish it up this week.
CURATOR-164 would be nice, but I'm not sure how those look from a compatibility viewpoint.
We should also pay attention to the ask in CURATOR-193 and make sure that we don't run into anything similar for 2.8.0.
Mike
On Tue, Apr 21, 2015 at 9:01 AM, Jordan Zimmerman <jo...@jordanzimmerman.com> wrote:
I think we have enough for a 2.8.0 release. Discuss now, please, if you’d like to see any other issues in the next release.
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314425&version=12329300
-Jordan
Re: Curator 2.8.0 (formerly 2.7.2)
Posted by Rodrigo Nogueira <ra...@gmail.com>.
I'm still using Curator 2.6.0 because of the CURATOR-188 issue. Any idea
when it will be fixed ?
On Tue, Apr 21, 2015 at 5:17 PM, Ricardo Ferreira <ri...@gmail.com>
wrote:
> I'd also like to see CURATOR-192 included. It seems an easy enough fix
> that can still be part of a next release.
>
> On Tue, Apr 21, 2015 at 5:09 PM, Mike Drob <md...@apache.org> wrote:
>
>> I'd like to see CURATOR-204. I'll check later today if there is an
>> apache-parent-17 that we should be using instead of 16, even.
>>
>> Maybe we can also do CURATOR-164, I'll try to finish it up this week.
>>
>> CURATOR-164 would be nice, but I'm not sure how those look from a
>> compatibility viewpoint.
>>
>> We should also pay attention to the ask in CURATOR-193 and make sure that
>> we don't run into anything similar for 2.8.0.
>>
>> Mike
>>
>> On Tue, Apr 21, 2015 at 9:01 AM, Jordan Zimmerman <
>> jordan@jordanzimmerman.com> wrote:
>>
>>> I think we have enough for a 2.8.0 release. Discuss now, please, if
>>> you’d like to see any other issues in the next release.
>>>
>>>
>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314425&version=12329300
>>>
>>> -Jordan
>>>
>>
>>
>
Re: Curator 2.8.0 (formerly 2.7.2)
Posted by Ricardo Ferreira <ri...@gmail.com>.
I'd also like to see CURATOR-192 included. It seems an easy enough fix that
can still be part of a next release.
On Tue, Apr 21, 2015 at 5:09 PM, Mike Drob <md...@apache.org> wrote:
> I'd like to see CURATOR-204. I'll check later today if there is an
> apache-parent-17 that we should be using instead of 16, even.
>
> Maybe we can also do CURATOR-164, I'll try to finish it up this week.
>
> CURATOR-164 would be nice, but I'm not sure how those look from a
> compatibility viewpoint.
>
> We should also pay attention to the ask in CURATOR-193 and make sure that
> we don't run into anything similar for 2.8.0.
>
> Mike
>
> On Tue, Apr 21, 2015 at 9:01 AM, Jordan Zimmerman <
> jordan@jordanzimmerman.com> wrote:
>
>> I think we have enough for a 2.8.0 release. Discuss now, please, if you’d
>> like to see any other issues in the next release.
>>
>>
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314425&version=12329300
>>
>> -Jordan
>>
>
>
Re: Curator 2.8.0 (formerly 2.7.2)
Posted by Mike Drob <md...@apache.org>.
I'd like to see CURATOR-204. I'll check later today if there is an
apache-parent-17 that we should be using instead of 16, even.
Maybe we can also do CURATOR-164, I'll try to finish it up this week.
CURATOR-164 would be nice, but I'm not sure how those look from a
compatibility viewpoint.
We should also pay attention to the ask in CURATOR-193 and make sure that
we don't run into anything similar for 2.8.0.
Mike
On Tue, Apr 21, 2015 at 9:01 AM, Jordan Zimmerman <
jordan@jordanzimmerman.com> wrote:
> I think we have enough for a 2.8.0 release. Discuss now, please, if you’d
> like to see any other issues in the next release.
>
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314425&version=12329300
>
> -Jordan
>