You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geode.apache.org by Brian Proffitt <bk...@apache.org> on 2026/01/08 20:58:39 UTC
Upcoming Geode-related content
Hey Geode folks,
First off I want to thank those of you who have been working on
creating excellent content about your revitalized project. Because of
the holiday break, M&P now has drafts and finished articles on:
* Geode 2.0 Release Announcement
* Apache Ozone / DiDi Global Case Study
* Apache Geode 2.0: A Modernization Epic
To spread out the distribution of this content, I am recommending this timing:
Geode 2.0 Release Announcement: to be posted/announced on January 12 (or ASAP)
Apache Ozone / DiDi Global Case Study: finished, to be posted on
apache.org in late January/early Feb, then syndicated later on Dev.to
Apache Geode 2.0: A Modernization Epic: Draft received, which is very
lengthy, and we would like to discuss here how to possibly split it
into two or three parts, and then figure out the timing of these posts
(every two weeks?)
We can discuss the order and timing aspects as you like, but M&P is
set on doing the 2.0 announcement first due to sheer timeliness.
Thanks for the discussion to come and the work thus far!
BKP
Brian Proffitt
VP, Marketing & Publicity
VP, Conferences
Re: Upcoming Geode-related content
Posted by Brian Proffitt <bk...@apache.org>.
Jinwoo,
No, your suggestion won't work as written. You are either the "Release
Manager for the Apache Geode project" OR "Release Manager for the
Apache Geode 2.0 release". There really should be no such thing as an
"Apache Geode 2.0 project".
Let me know which one you prefer, but honestly, the way it is written
now is fine.
BKP
Brian Proffitt
VP, Marketing & Publicity
VP, Conferences
On Mon, Jan 12, 2026 at 12:32 PM Whitney True <wh...@constantia.io> wrote:
>
> Jinwoo's request re: rewording in his quote.
>
> ---------- Forwarded message ---------
> From: Jinwoo Hwang <Ji...@sas.com>
> Date: Mon, Jan 12, 2026 at 9:26 AM
> Subject: Re: Upcoming Geode-related content
> To: Whitney True <wh...@constantia.io>
>
>
> Hi Whitney,
>
> Thank you so much for coordinating and sharing the Apache Geode 2.0 announcement. I appreciate your support and the visibility you’ve helped bring to the community.
>
>
> Would it be possible to update the wording to “Apache Geode 2.0 Project” for accuracy?
> “This release is more than an upgrade—it is a full-scale transformation of Apache Geode,” said Jinwoo Hwang, Lead Developer, Project Lead, and Release Manager for Apache Geode 2.0 Project.
>
>
> Best regards,
>
> Jinwoo Hwang (he/him/his)
>
>
>
> SAS® Research and Development
>
> http://JinwooHwang.com
>
>
>
> From: Whitney True <wh...@constantia.io>
> Date: Monday, January 12, 2026 at 12:12 PM
> To: dev@geode.apache.org <de...@geode.apache.org>, private@geode.apache.org <pr...@geode.apache.org>
> Cc: Jinwoo Hwang <Ji...@sas.com>, markpub@apache.org <ma...@apache.org>
> Subject: Re: Upcoming Geode-related content
>
> EXTERNAL
>
> This email is confirming that the Apache Geode 2.0 press announcement has been issued this morning on a newswire and posted to ASF social and web channels.
>
> Providing links here for easy reference and sharing:
>
> Apache.org: https://news.apache.org/foundation/entry/the-apache-software-foundation-announces-apache-geode-2-0
>
> LinkedIn: https://www.linkedin.com/posts/the-apache-software-foundation_opensource-activity-7416526194541527040-c7M8
>
> Bluesky: https://bsky.app/profile/apache.org/post/3mcajnkojyp25
>
> Twitter/X: https://x.com/TheASF/status/2010760420517089780
>
> Congratulations to the Geode community for achieving this milestone!
>
> Best,
> ASF M&P Team
>
> On Thu, Jan 8, 2026 at 4:40 PM Jinwoo Hwang via markpub <ma...@apache.org> wrote:
>
> Hi Brian,
>
> Thank you very much for the update and for all the coordination from M&P. I appreciate the thoughtful approach to pacing the content and completely agree with the proposed order. Prioritizing the Geode 2.0 Release Announcement on January 12 makes perfect sense given its timeliness.
>
> The plan for the Ozone and DiDi case study and the Modernization Epic series also sounds great. I am fully supportive of splitting the modernization article into multiple parts and discussing the best structure and cadence.
>
> Thank you again for your guidance and partnership. I am looking forward to the upcoming discussions and to helping move everything forward.
>
>
> Best regards,
>
> Jinwoo Hwang (he/him/his)
>
>
>
> SAS® Research and Development
>
> http://JinwooHwang.com<http://jinwoohwang.com/>
>
>
>
> From: Brian Proffitt <bk...@apache.org>
> Date: Thursday, January 8, 2026 at 3:59 PM
> To: ASF M&P Ops <ma...@apache.org>, dev@geode.apache.org <de...@geode.apache.org>
> Subject: Upcoming Geode-related content
>
> EXTERNAL
>
> Hey Geode folks,
>
> First off I want to thank those of you who have been working on
> creating excellent content about your revitalized project. Because of
> the holiday break, M&P now has drafts and finished articles on:
>
> * Geode 2.0 Release Announcement
> * Apache Ozone / DiDi Global Case Study
> * Apache Geode 2.0: A Modernization Epic
>
> To spread out the distribution of this content, I am recommending this timing:
>
> Geode 2.0 Release Announcement: to be posted/announced on January 12 (or ASAP)
>
> Apache Ozone / DiDi Global Case Study: finished, to be posted on
> apache.org in late January/early Feb, then syndicated later on Dev.to
>
> Apache Geode 2.0: A Modernization Epic: Draft received, which is very
> lengthy, and we would like to discuss here how to possibly split it
> into two or three parts, and then figure out the timing of these posts
> (every two weeks?)
>
> We can discuss the order and timing aspects as you like, but M&P is
> set on doing the 2.0 announcement first due to sheer timeliness.
>
> Thanks for the discussion to come and the work thus far!
>
> BKP
>
> Brian Proffitt
> VP, Marketing & Publicity
> VP, Conferences
>
Re: Upcoming Geode-related content
Posted by Jinwoo Hwang via dev <de...@geode.apache.org>.
Hi Brian,
Thank you very much for the update and for all the coordination from M&P. I appreciate the thoughtful approach to pacing the content and completely agree with the proposed order. Prioritizing the Geode 2.0 Release Announcement on January 12 makes perfect sense given its timeliness.
The plan for the Ozone and DiDi case study and the Modernization Epic series also sounds great. I am fully supportive of splitting the modernization article into multiple parts and discussing the best structure and cadence.
Thank you again for your guidance and partnership. I am looking forward to the upcoming discussions and to helping move everything forward.
Best regards,
Jinwoo Hwang (he/him/his)
SAS® Research and Development
http://JinwooHwang.com<http://jinwoohwang.com/>
From: Brian Proffitt <bk...@apache.org>
Date: Thursday, January 8, 2026 at 3:59 PM
To: ASF M&P Ops <ma...@apache.org>, dev@geode.apache.org <de...@geode.apache.org>
Subject: Upcoming Geode-related content
EXTERNAL
Hey Geode folks,
First off I want to thank those of you who have been working on
creating excellent content about your revitalized project. Because of
the holiday break, M&P now has drafts and finished articles on:
* Geode 2.0 Release Announcement
* Apache Ozone / DiDi Global Case Study
* Apache Geode 2.0: A Modernization Epic
To spread out the distribution of this content, I am recommending this timing:
Geode 2.0 Release Announcement: to be posted/announced on January 12 (or ASAP)
Apache Ozone / DiDi Global Case Study: finished, to be posted on
apache.org in late January/early Feb, then syndicated later on Dev.to
Apache Geode 2.0: A Modernization Epic: Draft received, which is very
lengthy, and we would like to discuss here how to possibly split it
into two or three parts, and then figure out the timing of these posts
(every two weeks?)
We can discuss the order and timing aspects as you like, but M&P is
set on doing the 2.0 announcement first due to sheer timeliness.
Thanks for the discussion to come and the work thus far!
BKP
Brian Proffitt
VP, Marketing & Publicity
VP, Conferences