Cancelling the vote on this release candidate due to concerns about breaking
backwards compatibility in a patch release.
Anthony
> On Aug 25, 2017, at 3:20 PM, Anthony Baker wrote:
>
> This is the first release candidate for Apache Geode, version 1.2.1.
> Thanks to all the community members fo
If this change is for security reasons I think it should be introduced in
whatever way is necessary mitigate any security issues by default.
> On Sep 5, 2017, at 3:31 PM, Anthony Baker wrote:
>
> Ok, I understand and agree this approach, even though it means spinning
> another RC.
>
> Other t
Ok, I understand and agree this approach, even though it means spinning another
RC.
Other thoughts?
Anthony
> On Sep 5, 2017, at 11:04 AM, Michael Stolz wrote:
>
> GEODE-3249 is a breaking change to the client/server protocol, but it has a
> property that can override whether or not to turn t
GEODE-3249 is a breaking change to the client/server protocol, but it has a
property that can override whether or not to turn the breaking change on.
The plan was to release Geode 1.2.1 with the breaking change turned on, but
I spent a lot of time thinking about this over the weekend, and I came t
I've pushed the fix for the problem with geode-3249 to develop and
cherry-picked it on the release/1.2.1 branch
On 8/30/17 2:59 PM, Anthony Baker wrote:
This vote is cancelled due to an error an in the fix for GEODE-3249.
Anthony
On Wed, Aug 30, 2017 at 10:25 AM, Bruce Schuchardt
wrote:
W
This vote is cancelled due to an error an in the fix for GEODE-3249.
Anthony
On Wed, Aug 30, 2017 at 10:25 AM, Bruce Schuchardt
wrote:
> We've found a problem with the fix for geode-3249 that should probably be
> corrected in the 1.2.1 release.
>
>
>
> On 8/29/17 12:07 PM, Anthony Baker wrote:
We've found a problem with the fix for geode-3249 that should probably
be corrected in the 1.2.1 release.
On 8/29/17 12:07 PM, Anthony Baker wrote:
I encourage the PMC members to review and vote so we can close out this
release. Of course, all feedback is welcome.
Thanks,
Anthony
On Aug 2
I am not filling your upgrade steps? You say upgrade clients in both steps 2
and 3. What does that mean?
Sent from my iPhone
> On Aug 29, 2017, at 1:38 PM, Anthony Baker wrote:
>
> Hi Mike!
>
> Thanks for your feedback. IMHO I don't consider GEODE-3249 to break
> client/server compatibility
I think in number 3 you mean remove flag and restart servers.
That should work.
Ok, +1
--
Mike Stolz
Principal Engineer, GemFire Product Manager
Mobile: +1-631-835-4771
On Tue, Aug 29, 2017 at 4:38 PM, Anthony Baker wrote:
> Hi Mike!
>
> Thanks for your feedback. IMHO I don't consider GEODE-3
Hi Mike!
Thanks for your feedback. IMHO I don't consider GEODE-3249 to break
client/server compatibility since there's a mechanism to disable the
protocol change to allow clients to be upgraded. The process would
look like this:
1) Upgrade servers and set the
'geode.allow-internal-messages-with
-1 for breaking change in client/server protocol.
--
Mike Stolz
Principal Engineer, GemFire Product Manager
Mobile: +1-631-835-4771
On Tue, Aug 29, 2017 at 3:07 PM, Anthony Baker wrote:
> I encourage the PMC members to review and vote so we can close out this
> release. Of course, all feedback
I encourage the PMC members to review and vote so we can close out this
release. Of course, all feedback is welcome.
Thanks,
Anthony
> On Aug 25, 2017, at 3:20 PM, Anthony Baker wrote:
>
> This is the first release candidate for Apache Geode, version 1.2.1.
> Thanks to all the community membe
This is the first release candidate for Apache Geode, version 1.2.1.
Thanks to all the community members for their contributions to this
release!
*** Please download, test and vote by Wednesday, August 25, 0800 hrs
US Pacific. ***
It fixes the following issues:
https://issues.apache.org/jira/s
13 matches
Mail list logo
