Added to blocker list. Thanks for raising this now, and a good reminder that
when we do get to 1.14.0.RC1, some extra scrutiny on legal/license-y stuff will
be a good thing for PMC members to include in their review.
On 3/17/21, 1:49 PM, "Joris Melchior" wrote:
+1
On 2021-03-17, 2:
+1
On 2021-03-17, 2:43 PM, "Hale Bales" wrote:
Hello,
I am putting forward the proposal to backport GEODE-9045 (Rename Redis
properties and error messages) to support/1.14 branch,
What does GEODE-9045 do?
* It renames the redis-port property to
com
+1
From: Hale Bales
Sent: Wednesday, March 17, 2021 11:42 AM
To: dev@geode.apache.org
Subject: [Proposal] Backport GEODE-9045 to support/1.14
Hello,
I am putting forward the proposal to backport GEODE-9045 (Rename Redis
properties and error messages) to
Seems like a no-brainer given the very low risk in the change and that it comes
with legal reasons
From: Hale Bales
Sent: Wednesday, March 17, 2021 11:42
To: dev@geode.apache.org
Subject: [Proposal] Backport GEODE-9045 to support/1.14
Hello,
I am putting
Hello,
I am putting forward the proposal to backport GEODE-9045 (Rename Redis
properties and error messages) to support/1.14 branch,
What does GEODE-9045 do?
* It renames the redis-port property to
compatible-with-redis-port
* It renames the redis-bind-
