geode-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Anthony Baker <aba...@pivotal.io>
Subject Re: release 1.2
Date Wed, 14 Jun 2017 23:59:16 GMT
Agreed.  Please merge to release/1.2.0 when ready.

Anthony

> On Jun 14, 2017, at 1:46 PM, Lynn Hughes-Godfrey <lhughesgodfrey@pivotal.io> wrote:
> 
> We would like to include the fix for (GEODE-3072) Events do not get removed
> from the client queue when 1.0 clients connect to 1.2 servers
> 
> On Wed, Jun 14, 2017 at 12:25 PM, Fred Krone <fkrone@pivotal.io> wrote:
> 
>> Reviewing our JTA transaction manager implementation during a recent issue
>> we thought it would be useful to log message for users when our
>> implementation is being used (which is by default but potentially unknown).
>> 
>> 
>> It's small but not critical -- we thought we might get it in if the 1.2
>> release lingered.  Eric was running pre-check-in on it.
>> 
>> On Wed, Jun 14, 2017 at 12:17 PM, Anthony Baker <abaker@pivotal.io> wrote:
>> 
>>> 
>>>> On Jun 14, 2017, at 12:03 PM, Eric Shu <eshu@pivotal.io> wrote:
>>>> 
>>>> I'd like to include GEODE-2301 in the release 1.2.0 (deprecate GEODE
>>>> implementation of JTA transaction manager)
>>>> 
>>>> -Eric
>>> 
>>> Thanks Eric.  Can you make a case for why this change needs to go into
>>> 1.2.0?  We’re pretty locked down on 1.2.0 changes and unless it’s a
>>> critical issue I’d prefer to not introduce more changes.
>>> 
>>> Has the deprecation of this feature been discussed?
>>> 
>>> Anthony
>>> 
>>> 
>> 


Mime
View raw message