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 dunit and integration tests for Redis HMGET
GEODE-8624: Improve INCRBYFLOAT accuracy for very large values
Not accepted yet:
GEODE-8864: finish implementation of Redis HSCAN Command
GEODE-8859: Redis data structures may not accurately reflect their size in
Geode stats
GEODE-8965: Implement Redis “noevict” policy for Geode Redis
On 2/26/21, 1:46 PM, "Raymond Ingles" <ring...@vmware.com> 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 are still in flight but
close to completion.)
On 2/26/21, 12:09 PM, "Owen Nichols" <onich...@vmware.com> wrote:
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, "Owen Nichols" <onich...@vmware.com> wrote:
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 you
need.
On 2/12/21, 1:20 AM, "Owen Nichols" <onich...@vmware.com> wrote:
support/1.14 has been cut. Any fixes 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]
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fsecure%2FDashboard.jspa%3FselectPageId%3D12336052&data=04%7C01%7Cringles%40vmware.com%7C4bb0c63928e2424e64ce08d8da86cab3%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C1%7C0%7C637499619749705983%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=GUnp%2BlwJx63jfJNGUqBJPoHMS70kfTiBrbRKdCUwg5Y%3D&reserved=0
On 2/10/21, 8:49 AM, "Owen Nichols" <onich...@vmware.com> wrote:
Sounds good.
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 Nichols
1.14.0 Release Manager
On 2/9/21, 11:54 AM, "Alexander Murmann"
<amurm...@vmware.com> wrote:
Hi everyone,
We aren't seeing many issues that would prevent a
1.14.0 release on our blocker board <
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fsecure%2FDashboard.jspa%3FselectPageId%3D12336052&data=04%7C01%7Cringles%40vmware.com%7C4bb0c63928e2424e64ce08d8da86cab3%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C1%7C0%7C637499619749715974%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=WBc%2FT8lqEvmLW0ACjYXcYBHzo0PxQrp3W%2Fzm2IeP%2B1U%3D&reserved=0>
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 1.14 release branch and get us on track
to ship Apache Geode 1.14.0 in early March.
I propose we cut the branch at the end of this week and
aim to ship 4 weeks later, on March 12th.
