Mailing-List: contact user-help@curator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@curator.apache.org
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: DISCUSS: Remove Classic connection handling
From: Jordan Zimmerman <jordan@jordanzimmerman.com>
In-Reply-To: <CAFAMeYJcML0qVq2hKr6jJK72orb-pokV0Jz3SpLoT7X54JhpFg@mail.gmail.com>
Date: Mon, 24 Jul 2017 08:58:48 -0500
Cc: user@curator.apache.org
Content-Transfer-Encoding: 7bit
Message-Id: <79C1DCEC-7729-4373-A389-D829F40DAECE@jordanzimmerman.com>
References: <70DF7FF7-C510-432A-80CA-58EDC93B4A67@jordanzimmerman.com>
 <CAFAMeYJcML0qVq2hKr6jJK72orb-pokV0Jz3SpLoT7X54JhpFg@mail.gmail.com>
To: dev@curator.apache.org
archived-at: Mon, 24 Jul 2017 13:58:55 -0000

It will show in the release notes.

> On Jul 24, 2017, at 8:28 AM, Mike Drob <mdrob@apache.org> wrote:
> 
> To clarify, this means that folks still on Curator 2.x will see a change in
> behavior if they go straight to 4.x? It's a major version, so that should
> be fine but let's make sure it shows up in the release notes.
> 
> On Mon, Jul 24, 2017 at 12:01 AM, Jordan Zimmerman <
> jordan@jordanzimmerman.com> wrote:
> 
>> Background: We are preparing to release what will be Apache Curator 4.0.0.
>> As usual, our tests are a bit flakey. Currently, the biggest culprit is
>> "classic" connection handling. This is a special internal mode that most
>> people probably don't even know about. It was added as a backward
>> compatibility stop gap when the meaning of connection state LOST changed
>> from Curator 2.x to Curator 3.x. With Curator 4.0, I'd like to completely
>> remove "classic" connection handling unless there are objections. Here is
>> the PR:
>> 
>>        https://github.com/apache/curator/pull/233 <
>> https://github.com/apache/curator/pull/233>
>> 
>> Please comment on the PR if you have any issues with this. I'll leave this
>> open for 48 hours - i.e. barring objections this will get merged Wednesday
>> morning US time.
>> 
>> -Jordan