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 2017/07/19 19:48:04 UTC

Proposal: end-of-life for Curator 2.0 and make next version 4.0.0

Folks,

I was trying to backport some PRs to CURATOR-2.0 and it was very difficult. So, I decided to see what it would take to make Curator 3.x work with ZooKeeper 3.4.x. The result is https://issues.apache.org/jira/browse/CURATOR-425 <https://issues.apache.org/jira/browse/CURATOR-425>. There will be a PR later today (barring anything unforeseen). Given this, there's no reason to continue with CURATOR-2.0. Also, given the number of changes and new features in master, I propose that we make the next release Curator 4.0.0. 

Any objections/comments?

-Jordan

Re: Proposal: end-of-life for Curator 2.0 and make next version 4.0.0

Posted by Jordan Zimmerman <jo...@jordanzimmerman.com>.
Thanks Cameron. I'll do the release, no worries.

-JZ

> On Jul 22, 2017, at 2:55 AM, Cameron McKenzie <ca...@apache.org> wrote:
> 
> Sounds ok to me as long as the backwards compatibility is all good. I'm still away for another couple of days, but I can do the release sometime next week if you like.
> cheers 
> 
> On Thu, Jul 20, 2017 at 5:48 AM, Jordan Zimmerman <jordan@jordanzimmerman.com <ma...@jordanzimmerman.com>> wrote:
> Folks,
> 
> I was trying to backport some PRs to CURATOR-2.0 and it was very difficult. So, I decided to see what it would take to make Curator 3.x work with ZooKeeper 3.4.x. The result is https://issues.apache.org/jira/browse/CURATOR-425 <https://issues.apache.org/jira/browse/CURATOR-425>. There will be a PR later today (barring anything unforeseen). Given this, there's no reason to continue with CURATOR-2.0. Also, given the number of changes and new features in master, I propose that we make the next release Curator 4.0.0. 
> 
> Any objections/comments?
> 
> -Jordan
> 


Re: Proposal: end-of-life for Curator 2.0 and make next version 4.0.0

Posted by Jordan Zimmerman <jo...@jordanzimmerman.com>.
I've proven that it works by running all the framework/recipe tests with the latest master but forcing ZooKeeper 3.4.8 as the client library and server (via curator-test 2.12.0).

> On Jul 22, 2017, at 2:55 AM, Cameron McKenzie <ca...@apache.org> wrote:
> 
> Sounds ok to me as long as the backwards compatibility is all good


Re: Proposal: end-of-life for Curator 2.0 and make next version 4.0.0

Posted by Jordan Zimmerman <jo...@jordanzimmerman.com>.
Thanks Cameron. I'll do the release, no worries.

-JZ

> On Jul 22, 2017, at 2:55 AM, Cameron McKenzie <ca...@apache.org> wrote:
> 
> Sounds ok to me as long as the backwards compatibility is all good. I'm still away for another couple of days, but I can do the release sometime next week if you like.
> cheers 
> 
> On Thu, Jul 20, 2017 at 5:48 AM, Jordan Zimmerman <jordan@jordanzimmerman.com <ma...@jordanzimmerman.com>> wrote:
> Folks,
> 
> I was trying to backport some PRs to CURATOR-2.0 and it was very difficult. So, I decided to see what it would take to make Curator 3.x work with ZooKeeper 3.4.x. The result is https://issues.apache.org/jira/browse/CURATOR-425 <https://issues.apache.org/jira/browse/CURATOR-425>. There will be a PR later today (barring anything unforeseen). Given this, there's no reason to continue with CURATOR-2.0. Also, given the number of changes and new features in master, I propose that we make the next release Curator 4.0.0. 
> 
> Any objections/comments?
> 
> -Jordan
> 


Re: Proposal: end-of-life for Curator 2.0 and make next version 4.0.0

Posted by Jordan Zimmerman <jo...@jordanzimmerman.com>.
I've proven that it works by running all the framework/recipe tests with the latest master but forcing ZooKeeper 3.4.8 as the client library and server (via curator-test 2.12.0).

> On Jul 22, 2017, at 2:55 AM, Cameron McKenzie <ca...@apache.org> wrote:
> 
> Sounds ok to me as long as the backwards compatibility is all good


Re: Proposal: end-of-life for Curator 2.0 and make next version 4.0.0

Posted by Cameron McKenzie <ca...@apache.org>.
Sounds ok to me as long as the backwards compatibility is all good. I'm
still away for another couple of days, but I can do the release sometime
next week if you like.
cheers

On Thu, Jul 20, 2017 at 5:48 AM, Jordan Zimmerman <
jordan@jordanzimmerman.com> wrote:

> Folks,
>
> I was trying to backport some PRs to CURATOR-2.0 and it was very
> difficult. So, I decided to see what it would take to make Curator 3.x work
> with ZooKeeper 3.4.x. The result is https://issues.apache.org/
> jira/browse/CURATOR-425. There will be a PR later today (barring anything
> unforeseen). Given this, there's no reason to continue with CURATOR-2.0.
> Also, given the number of changes and new features in master, I propose
> that we make the next release Curator 4.0.0.
>
> Any objections/comments?
>
> -Jordan
>

Re: Proposal: end-of-life for Curator 2.0 and make next version 4.0.0

Posted by Cameron McKenzie <ca...@apache.org>.
Sounds ok to me as long as the backwards compatibility is all good. I'm
still away for another couple of days, but I can do the release sometime
next week if you like.
cheers

On Thu, Jul 20, 2017 at 5:48 AM, Jordan Zimmerman <
jordan@jordanzimmerman.com> wrote:

> Folks,
>
> I was trying to backport some PRs to CURATOR-2.0 and it was very
> difficult. So, I decided to see what it would take to make Curator 3.x work
> with ZooKeeper 3.4.x. The result is https://issues.apache.org/
> jira/browse/CURATOR-425. There will be a PR later today (barring anything
> unforeseen). Given this, there's no reason to continue with CURATOR-2.0.
> Also, given the number of changes and new features in master, I propose
> that we make the next release Curator 4.0.0.
>
> Any objections/comments?
>
> -Jordan
>