Thank you all for the valuable feedback, below is the final draft, please do
let me know if this is anything more to add.
> ## Description:
> The mission of Apache Geode is the creation and maintenance of software
> related
> to a data management platform that provides real-time, consistent acces
Sounds good. BTW, I don't mean to discount all the hard work folks did getting
these patches out quickly. Thanks again for everyone who helped with that
effort!
-Dan
From: Owen Nichols
Sent: Friday, February 4, 2022 2:52 PM
To: dev@geode.apache.org
Subject: Re:
That's a much better way to put it, Mark. Thanks!
On 2/4/22, 2:50 PM, "Mark Bretl" wrote:
I agree with Dan here that bragging about 'one of the quickest' is not
needed, but noting we are up-to-date with Log4J patches and have
documentation for mitigation might be a better approach.
I agree with Dan here that bragging about 'one of the quickest' is not
needed, but noting we are up-to-date with Log4J patches and have
documentation for mitigation might be a better approach.
My $.02
--Mark
On Fri, Feb 4, 2022 at 11:34 AM Dan Smith wrote:
> Counting the kafka connector I'm no
Thanks for putting together this script, Dan. It's always humbling to discover
ways that a user's environment can differ from the tightly-controlled
conditions of CI.
I've noticed we've shipped quite a few releases recently with the bare minimum
of votes. I hope this will encourage more parti
Hi all,
I'd like to suggest something that might make voting on releases a little
clearer and easier. I feel like we've been a bit vague about what kind of
testing PMC members are supposed to do on a release candidate, and I see
different folks (including myself) running different kinds of ad h
Counting the kafka connector I'm not sure bragging about CVE patching speed is
justified, but otherwise looks good to me!
-Dan
From: Nabarun Nag
Sent: Tuesday, February 1, 2022 2:25 PM
To: dev@geode.apache.org
Subject: Re: [DRAFT] Apache Geode Board report due b
