Hi Cloudberry community, As we enter 2026, I’d like to start an open discussion about possible directions and priorities for Apache Cloudberry this year. These are personal thoughts and initial ideas, not decisions — the goal is to gather feedback, hear different perspectives, and shape the roadmap together as a community.
Overall, I believe we should continue evolving along our existing roadmap, with a clear long-term goal of moving toward graduation. Below are some topics and directions for discussion which we should focus on in 2026: 1. Kernel Upgrade * Complete the PostgreSQL kernel upgrade from PG14 to PG16 * After the upgrade: - Continuous testing and stability improvements - Compatibility work for ecosystem components and extensions 2. Release 2.1 Release cadence & maintenance branches In 2025, we shipped one Apache release. In 2026, I think we should increase release frequency — Potentially targeting something like one release per quarter (subject to community capacity and interest). For the 2.x series: - Ensure users already on 2.x can receive updates and fixes - Continue maintaining and evolving it (2.1 in the progress, possibly 2.2, 2.3, etc.) 2.2 Distribution & packaging Provide user-friendly artifacts: - RPM / DEB binary packages - Docker images This is important for adoption — I’ve heard repeated feedback that building from source is a barrier for many users. 3. CI & Engineering Infrastructure * Support more OS versions in CI workflows (related discussion: https://lists.apache.org/thread/jh7fkw0mk43bdfpjm939xphmq77yx24f) * For release branches: Binary swap CI (already supported) * Consider ABI compatibility testing Strengthen CI as part of long-term stability and release quality. 4. Performance & Cost Efficiency Performance remains a key selection factor for users. At the same time, TCO (Total Cost of Ownership) is becoming increasingly important. We should think about: * Performance optimization directions: PAX, vectorized execution, ORCA? * Resource efficiency * Lower the maintenance cost 5. Usability & Out-of-the-box Experience * Continue improving ease of use, especially integrating more extensions into Cloudberry for better “out-of-the-box” experience (related discussion: https://lists.apache.org/thread/o5n45tw6ok7wqpd7wdyhdgyhzlcs5t7j) 6. Ecosystem Integration * cross-Apache ecosystem Now the community developers are working on Cloudberry + Apache MADlib integration. Also, there is some community interest in integrating Apache AGE for graph processing. * other mostly used PG extensions 7. Community Growth & Adoption We need to continue building a diverse contributor community, identifying and supporting new contributors. ~~~ These are only starting points for discussion. Love to have more thoughts, priorities from you: * What feels most important for 2026? * What are we missing? * What do you think would most help adoption, stability, and long-term sustainability? Looking forward to your feedback and ideas — let’s shape Cloudberry’s 2026 together. Best, Dianjin Wang --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
