Re: Geode Jira Access Request

Hi Steve, apache ID “ssienkowski” should be assignable to GEODE Jira tickets now. From: Steve Sienkowski Reply-To: "dev@geode.apache.org" Date: Monday, January 31, 2022 at 2:19 PM To: "dev@geode.apache.org" Subject: Geode Jira Access Request Hi team, Could someone help me get the proper

Re: Geode Jira Access Request

Many thanks, Owen! From: Owen Nichols Date: Tuesday, February 1, 2022 at 10:55 AM To: dev@geode.apache.org Subject: Re: Geode Jira Access Request Hi Steve, apache ID “ssienkowski” should be assignable to GEODE Jira tickets now. From: Steve Sienkowski Reply-To: "dev@geode.apache.org" Date:

Re: Geode Jira Access Request

Steve’s user name is ssienkow...@vmware.com. From: Alexander Murmann Date: Monday, January 31, 2022 at 2:26 PM To: dev@geode.apache.org Subject: Re: Geode Jira Access Request What's your username, Steve? From: Steve Sienkowski Sent: Monday, January 31, 2022

Re: [DRAFT] Apache Geode Board report due by Wed Feb 9th

1.12.8 seems to be missing from the list of releases. Also consider bragging about Geode’s turnaround time from CvE disclosure to patch release…only one other ASF project got theirs out faster than we did. --- Sent from Workspace ONE Boxer On January 31,

Re: [DRAFT] Apache Geode Board report due by Wed Feb 9th

Thank you for the feedback, please find the new draft with the added review comments. ## Project Activity: We issued 9 releases this quarter which include an updated Log4j2 version to handle the remote code execution CVE. The project had one of the quickest turnaround times from the Log4j2 CVE

Re: Question regarding geode thread priorities

Hi Kirk, No problem and thank you for the answer! Best Regards :), Jakov On 27. 01. 2022. 00:42, Kirk Lund wrote: PS: Sorry if I didn't realize what BRs is :D On Wed, Jan 26, 2022 at 3:39 PM Kirk Lund wrote: Hi BRs/Jakov, I'm familiar with most of these threads, and these ones I know of