Re: [DISCUSS] Cutting a Geode 1.14.0 release branch

Weeks since support/1.14 cut: 5 Changes backported this week: 7 Blockers we are still waiting on: 8 As of today I am no longer serving as Geode 1.14 Release Manager. Please volunteer if you would like to take over. On 3/12/21, 3:09 PM, "Owen Nichols" wrote: Weeks since support/1.14

Re: [DISCUSS] Cutting a Geode 1.14.0 release branch

Weeks since support/1.14 cut: 4 Blockers backported this week: 9 Blockers we are still waiting on: 9 If there's anything else we should be waiting on, please make a proposal to add it to the blocker board sooner rather than later (even if you're still investigating...fix doesn't have to be

Re: [DISCUSS] Cutting a Geode 1.14.0 release branch

It's been three weeks since support/1.14 was cut. This week, backports for 12 blockers arrived on support/1.14. Great job! As of now, the blocker board [1] shows that we are waiting on 9 blockers. Once this list reaches zero, I can prepare RC1. [1]

Re: [DISCUSS] Cutting a Geode 1.14.0 release branch

Since redis effort has been a big theme for 1.14, it makes sense to polish what's there as best as possible for its first release. Thanks for putting together this list, it feels like these are finishing touches and low risk, so I'll add them to the 1.14.0 blocker board. On 3/1/21, 11:57

Re: [DISCUSS] Cutting a Geode 1.14.0 release branch

We're actually hoping to get a few things into 1.14 to help make the compatibility with Redis to be useful: Merged to develop: GEODE-8933: Report max memory setting in Geode Redis statistics GEODE-8894: Allow individual deltas to trigger bucket size recalculation GEDOE-8865: Create additional

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] Cutting a Geode 1.14.0 release branch

It's been two weeks since support/1.14 was cut, and the 1.14.0 blocker board[1] still lists 5 issues (1 still Unassigned). Given the lack of activity on GEODE-8943, GEODE-8860, and GEODE-8809, should we defer them to 1.14.1 if we still "aim to ship on March 12th."? On 2/18/21, 10:00 AM,

Re: [DISCUSS] Cutting a Geode 1.14.0 release branch

It's been about a week since support/1.14 was cut, and the 1.14.0 blocker board [1] still lists 5 issues (two of which appear to be Unassigned). If a fix is taking longer than expected, please consider posting a status update in the ticket about once a week, and ask for help on the dev list if

Re: [DISCUSS] Cutting a Geode 1.14.0 release branch

support/1.14 has been cut. Any bugs fixed on develop from today onward should be marked as Fixed In 1.15.0. The 1.14.0 blocker board [1] currently lists 5 issues. RC1 won't be created before this list gets to zero. To add to the blocker board, please propose on the dev list. [1]

Re: [DISCUSS] Cutting a Geode 1.14.0 release branch

Sounds good to me. Once cut, only fixes from the blocker board may be brought to support/1.14. After Feb 12, if you wish to add a critical issue to the blocker board, please propose it on the dev list. If the community agrees it is critical, you may tag it as "blocks-1.14.0" Thanks, Owen

[DISCUSS] Cutting a Geode 1.14.0 release branch

Hi everyone, We aren't seeing many issues that would prevent a 1.14.0 release on our blocker board and all issues have an owner. No new issues seem to be coming in either. This seems like a good time to finally cut a