[ANNOUNCE] Geode session track for ApacheCon @Home
HI all, With conferences going virtual due to current events, we have moved the former “Geode Summit” over to a dedicated track as part of the virtual ApacheCon event. Lucky for you, we have some great talk submissions on lots of interesting topics! The talks will be presented live (virtually) on Sept 29-30. You can see the talk line up here: https://www.apachecon.com/acah2020/tracks/ And you can register to attend here (free/donation): https://hopin.to/events/apachecon-home Last, check out this primer from Bob Glithero: https://twitter.com/ApacheGeode/status/1293967391467036673?s=20 I’ll see you there! Anthony
Re: JIRA issues for geode native developers
FWIW - Mike is listed on the committer roles of Geode [1]. Matthew is not yet. We typically offer JIRA permissions anytime someone asks to make it easier for them to contribute. Anthony [1] https://whimsy.apache.org/roster/committee/geode On Aug 21, 2020, at 12:06 PM, Dan Smith mailto:dasm...@vmware.com>> wrote: It looks like they weren’t listed as committers in JIRA. I added them, you should be able to assign them issues now! -Dan On Aug 21, 2020, at 11:00 AM, Blake Bender mailto:bbl...@vmware.com>> wrote: Hello, In the course of attempting to be a better Geode citizen yesterday, I attempted to assign a JIRA issue to one of the members of the geode native full-time dev team, and discovered that I couldn’t. In fact, neither of them (Mike Martell, Matthew Reddington) can be assigned GEODE JIRA issues. Does anyone know what setting/permission/etc is missing there, and how to fix? Thanks, Blake
Re: JIRA issues for geode native developers
Working now - thanks, Dan! On 8/21/20, 12:14 PM, "Dan Smith" wrote: It looks like they weren’t listed as committers in JIRA. I added them, you should be able to assign them issues now! -Dan > On Aug 21, 2020, at 11:00 AM, Blake Bender wrote: > > Hello, > > In the course of attempting to be a better Geode citizen yesterday, I attempted to assign a JIRA issue to one of the members of the geode native full-time dev team, and discovered that I couldn’t. In fact, neither of them (Mike Martell, Matthew Reddington) can be assigned GEODE JIRA issues. Does anyone know what setting/permission/etc is missing there, and how to fix? > > Thanks, > > Blake >
Re: JIRA issues for geode native developers
It looks like they weren’t listed as committers in JIRA. I added them, you should be able to assign them issues now! -Dan > On Aug 21, 2020, at 11:00 AM, Blake Bender wrote: > > Hello, > > In the course of attempting to be a better Geode citizen yesterday, I > attempted to assign a JIRA issue to one of the members of the geode native > full-time dev team, and discovered that I couldn’t. In fact, neither of them > (Mike Martell, Matthew Reddington) can be assigned GEODE JIRA issues. Does > anyone know what setting/permission/etc is missing there, and how to fix? > > Thanks, > > Blake >
JIRA issues for geode native developers
Hello, In the course of attempting to be a better Geode citizen yesterday, I attempted to assign a JIRA issue to one of the members of the geode native full-time dev team, and discovered that I couldn’t. In fact, neither of them (Mike Martell, Matthew Reddington) can be assigned GEODE JIRA issues. Does anyone know what setting/permission/etc is missing there, and how to fix? Thanks, Blake
Re: [PROPOSAL] Backport GEODE-8432 to 1.13
Thanks for your contribution, Gester On Thu, Aug 20, 2020 at 12:37 PM Joris Melchior wrote: > +1 > > On 2020-08-20, 12:08 PM, "Xiaojian Zhou" wrote: > > It's using region path instead of getting the region. It should be no > risk. > > On 8/19/20, 10:25 AM, "Xiaojian Zhou" wrote: > > This problem also exists in 1.13. > > >
