Re: Proposal: Cut 1.15 release branch from SHA 8f7193c827ee3198ae374101221c02039c70a561

BTW, just to clarify, when I officially proposed cutting the branch, I hadn't intended to volunteer as release manager this round. That said, it's important to branch at a point we're confident about. Bisecting a 3K-file change is potentially... complicated. If there's confidence we can track

Proposal: Cutting 1.15 Release branch Tuesday, 25 January

Hello Geode Dev Community, We have a proposal to cut the 1.15 release branch this coming Tuesday, the 25th of January, 2022. At this point it seems that development is feature-complete, and remaining work is on processing release-blocker bugs. Cutting the branch will allow new work to proceed

Re: Cleaning up the codebase - use curly braces everywhere

+1 Sounds like a good idea. Since always using curly braces is part of the style guide, fixing this makes sense. The only possible additional step for large-but-automatically-generated-and-specifically-targeted PRs like this is running the test suite with code coverage, making sure the updated

Apache ID for contributor status

Apparently there was a disconnect somewhere and I’ll need to contact the chair of the Geode PMC to request an Apache ID to establish contributor status. I’ve checked and ‘ringles’ is currently unused. How can I go about requesting the ID? I’ve already signed and sent the ICLA…

[Proposal] Backport GEODE-9029 - Initial support for Redis SLOWLOG command

Hello – Putting forward the proposal to backport GEODE-9029 (Redis SLOWLOG command support) to support/1.14 branch, What does GEODE-9029 do? * It adds unit/integration/dunit tests for the Redis SLOWLOG command * It moves the SLOWLOG command to the ‘Supported’ category

[Proposal] Backport GEODE-9009 - Support for Redis DECRBY command

Hello – Putting forward the proposal to backport GEODE-9009 (Redis DECRBY command support) to support/1.14 branch, What does GEODE-9009 do? * It adds unit/integration/dunit tests for the Redis DECRBY command * It moves the DECRBY command to the ‘Supported’

[Proposal] Backport GEODE-9022 to Apache Geode 1.14

Hello – Putting forward the proposal to backport GEODE-9022 (Redis INFO command support) to support/1.14 branch, What does GEODE-9022 do? * It adds unit/integration/dunit tests for the Redis INFO command * It moves the INFO command to the ‘Supported’ category

Re: [DISCUSS] Cutting a Geode 1.14.0 release branch

“noevict” policy for Geode Redis On 2/26/21, 1:46 PM, "Raymond Ingles" wrote: The Redis Compatibility effort has a few things we're hoping to backport to 1.14. I am putting together a list of tickets now and will report them later today. (Many of the tickets are done, and one or two

Proposal: new Geode property CRITICAL_HEAP_PERCENTAGE

The Geode Redis Compatibility code is working to emulate the Redis eviction policy “noevict”; when memory fills up, the server refuses new write commands until deletion or expiration has cleared space. Right now, part of the implementation is calling

Re: [DISCUSS] Cutting a Geode 1.14.0 release branch

The Redis Compatibility effort has a few things we're hoping to backport to 1.14. I am putting together a list of tickets now and will report them later today. (Many of the tickets are done, and one or two are still in flight but close to completion.) On 2/26/21, 12:09 PM, "Owen Nichols"

Re: [DISCUSS] One more 1.13 change

+1 On 9/28/20, 3:21 PM, "Dan Smith" wrote: Hi, I'd like to backport this change to support/1.13 as well GEODE-8522: Switching exception log back to debug -

Re: Proposal to bring GEODE-8456 (shiro upgrade) to support branches

+1 On 8/31/20, 7:19 PM, "Owen Nichols" wrote: Recently shiro-1.5.3.jar is getting flagged for ‘high’ security vulnerability CVE-2020-13933. Analysis shows that Geode does not use Shiro in a manner that would expose this vulnerability. The risk of bringing GEODE-8456 is low

Re: [PROPOSAL] Remove "Fix Version/s" and "Sprint" from Jira "Create Issue" dialogue and include "Affects Version/s"

+1 On 8/17/20, 3:04 PM, "Donal Evans" wrote: Looking at the dialogue that opens when you attempt to create a new ticket in the GEODE Jira[1], there are two fields included that aren't really necessary and may cause confusion. The "Fix Version/s" field should presumably not be filled out

Re: TimeIntegrationTest is flaky

Yes, we're on it. Thanks! On 8/12/20, 7:25 PM, "Kirk Lund" wrote: Since this is a new test, can we please prioritize fixing it?

Re: [PROPOSAL] one-time cleanup of stray and obsolete tags in geode repo

+1 On 7/30/20, 3:21 AM, "Owen Nichols" wrote: Tags in the rel/ namespace should be created by the Geode release manager as part of an official Geode release only, yet we seem to have some extra ones somehow. Further, I don't see any value in keeping RC tags forever long after the

Re: [DISCUSS] Geode Redis API Improvements

Just a quick nudge - we set a deadline for comments for tomorrow. Anyone had a chance to look this over yet? Thanks! On Thu, Apr 30, 2020 at 2:09 PM Raymond Ingles wrote: > Hi all, > > The current Redis API support in Geode has been marked experimental for a > couple years and has

[DISCUSS] Geode Redis API Improvements

Hi all, The current Redis API support in Geode has been marked experimental for a couple years and has several bugs and inconsistencies compared to native Redis. We created a RFC for updating the Geode Redis API support, to address issues in the implementation, improve performance and add High

Re: Wiki edit permissions

> > On Wed, Apr 29, 2020 at 11:20 AM Raymond Ingles > > wrote: > > > >> My colleague and I are hoping to add a new RFC to the Geode wiki, but we > >> need edit permissions to do it. I created an account on the wiki in the > >> name of ring...@vmware.com<

Wiki edit permissions

My colleague and I are hoping to add a new RFC to the Geode wiki, but we need edit permissions to do it. I created an account on the wiki in the name of ring...@vmware.com, and Sarah did so with the address sabbe...@gmail.com. Who should we

Request adding to the Geode project in JIRA

While I can log in (as 'ringles') to the Geode JIRA, I don't seem to be able to assign/be assigned JIRA tickets. Can I be added to whatever group allows that? Thanks!