Hi Dianjin and all, Great to see the discussion moving forward on the 2.1.0 release — the timing makes sense given the steady flow of commits since the 2.0.0 baseline.
In parallel, I’d also like to propose that we begin planning for releases of the following components: - Apache Cloudberry PXF <https://github.com/apache/cloudberry-pxf> - Apache Cloudberry Backup <https://github.com/apache/cloudberry-backup> Since these are separate Apache project repositories, each will require its own release process, including votes and corresponding artifacts. Coordinating these component releases alongside or shortly after 2.1.0 would help provide a version-aligned ecosystem for downstream users. Happy to help drive discussion around scope, testing, and coordination for these component releases as well. Best, -=e Ed Espino Apache Cloudberry (Incubating) & MADlib ------------------------------ On Wed, Oct 15, 2025 at 11:13 PM Dianjin Wang <[email protected]> wrote: > Hi all, > > Following our first release under the Apache Incubator — Apache > Cloudberry 2.0.0, which was published at the end of August, I’d like > to initiate a discussion about our next minor release. > > The core code baseline for 2.0.0 was frozen around early June. Since > then, nearly five months have passed, and there have been a large > number of new features, bug fixes, and enhancements merged into the > main branch. I believe it’s a good time to begin discussing the Apache > Cloudberry 2.1.0 release. > > I’d also like to thank Ed for initiating a related discussion earlier > on the mailing list[1]. This email aims to start a separate thread > focused specifically on the discussion for the 2.1.0 release. > > One thing to note is that some recent commits have introduced catalog > changes, which means we won’t be able to perform binary upgrades > directly from 2.0. We might need help from developer engineers to > identify and skip those incompatible commits. Currently, we don’t yet > have an automated ABI or catalog compatibility testing mechanism, so > this process will rely on manual verification, which could bring some > risks. > > Let’s discuss the possibility & possible timeline, scope, and any > preparations needed for the 2.1.0 release. Would like to have your > voices. > > [1] https://lists.apache.org/thread/2kbgympw994y48v7sz2d5mh48ptfy5of > > Best, > Dianjin Wang > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
