This is wonderful news. Congratulations, Jinwoo and everyone else who worked to 
make this migration happen. What a milestone!

Bryan

-----Original Messages-----

Jinwoo Hwang wrote:

Dear Apache Geode Developer Community,

I’m thrilled to announce that GEODE-10466: Jakarta EE 10 Migration has been 
successfully merged into the develop branch — a defining milestone on our path 
to Apache Geode 2.0.

This effort was far more than a technical upgrade. It marks Geode’s evolution 
into the Jakarta EE 10 ecosystem, bringing with it a modern foundation built on 
Spring Framework 6, Spring Boot 3, Spring Shell 3, and Jetty 12. These upgrades 
position Geode for long-term sustainability, stronger security, and a more 
vibrant future of innovation.

This achievement reflects the best of open collaboration. My heartfelt thanks 
go to Sai Boorlagadda, Leon Finker, and Arnout Engelen for their thoughtful 
reviews, deep expertise, and commitment to excellence throughout this 
transformation.

What’s Next
-We’ve entered a stabilization period on the develop branch.
-On December 1, I plan to create the support/2.0 branch.
-The Apache Geode 2.0.0 release could arrive as early as mid-December — a 
release that will define the next generation of Geode.

During this stabilization phase, community testing and feedback are vital.
If you maintain applications or deployments that depend on Geode, please take 
this opportunity to build and run against the latest develop branch, validate 
integration points, and report any regressions or unexpected behavior. Early 
testing helps us ensure that 2.0.0 delivers a smooth, reliable upgrade 
experience for everyone in the ecosystem.

How You Can Help
As we approach 2.0, your participation is more important than ever:
GEODE-10488
– Update geode-book documentation configuration
GEODE-10480
– Remediate critical security vulnerabilities in third-party dependencies


Nice to Have for 2.0.0 (Non-blocking, but Valuable)
GEODE-10479
– Address deprecation and removal warnings from Java 17 migration
GEODE-10468
– Modernize the Apache Geode website
GEODE-10481
– Implement Software Bill of Materials (SBOM) generation (led by Sai 
Boorlagadda)


Apache Geode 2.0.0 Project Dashboard
https://protect.checkpoint.com/v2/r01/___https://issues.apache.org/jira/projects/GEODE/versions/12356370___.YzJ1OnNhc2luc3RpdHV0ZTpjOm86YjhjNjg4N2QxZjRhMjNkZjUyM2QyM2MyNjM3MTk3MzU6Nzo3ZTViOjE4M2U0YjY3NjBmYzVmZTdiOGZlNTQzYjJiM2M3NjkyZDgyYmZmM2M0ZmU4MDVmYzg0ODI1YzlkYmI0NDE2Nzk6cDpUOk4
 
<https://protect.checkpoint.com/v2/r01/___https://issues.apache.org/jira/projects/GEODE/versions/12356370___.YzJ1OnNhc2luc3RpdHV0ZTpjOm86YjhjNjg4N2QxZjRhMjNkZjUyM2QyM2MyNjM3MTk3MzU6Nzo3ZTViOjE4M2U0YjY3NjBmYzVmZTdiOGZlNTQzYjJiM2M3NjkyZDgyYmZmM2M0ZmU4MDVmYzg0ODI1YzlkYmI0NDE2Nzk6cDpUOk4>

As we stabilize and refine the 2.0 branch, your feedback, testing, and 
observations will directly shape the release.
Whether it’s validating functionality, reviewing documentation updates, or 
testing backward compatibility scenarios — every contribution helps strengthen 
the release.

Please share your findings, suggestions, or concerns on the 
[email protected] <mailto:[email protected]> mailing list or directly in 
JIRA.
Your insights will help us ensure that Apache Geode 2.0 is not only modernized 
but also battle-tested, stable, and production-ready.
This is a pivotal moment for the project, and your voice truly matters.

Each milestone like this reminds us that Apache Geode’s strength lies not only 
in its code but in its community. Together, we are building a platform that 
continues to inspire innovation, uphold reliability, and embrace the future of 
distributed systems.

Thank you all for your continued dedication, collaboration, and vision. Through 
your collective effort, Apache Geode is evolving into a stronger, more modern, 
and future-ready platform. The progress we make today lays the groundwork for 
the next decade of innovation and ensures Geode’s continued growth and success 
as a leading open-source project.


Best regards,
Jinwoo Hwang (he/him/his)


Reply via email to