Hi all, With the successful release of Apache Cloudberry (Incubating) 2.0.0, I would like to open a discussion on possible next steps for releases across related components.
In particular, we may want to consider releases for the following: - https://github.com/apache/cloudberry-gpbackup - https://github.com/apache/cloudberry-gpbackup-s3-plugin - https://github.com/apache/cloudberry-pxf The exact version numbers for these components are still to be determined, but it may make sense to align them with the current 2.x line, or discuss whether a different scheme is preferable. We may also want to begin planning for a 3.x release based on the current state of the main branch. It feels unusual to wait for the PostgreSQL 16 merge and stabilization work before cutting a 3.x release. Another option is to release main as 3.x now, and then ship PG16 support in a subsequent release. It is also very likely that the PG16 merge will introduce catalog changes significant enough to warrant a future 4.x release. Some of these choices may require careful porting of changes across different release branches, so I think it is important to start the discussion early. I would like to hear the community’s thoughts on: - Releasing the above components, and how to assign versions. - Whether to cut a 3.x release from main sooner rather than later. - How best to manage porting between branches if needed. - Planning for a 4.x release once PG16 work is ready. Looking forward to your input. -=e -- Ed Espino Apache Cloudberry (Incubating) & MADlib
