Hi All, We need to consider when to release Cloudberry 2.0, and how often to release it, which involves the following considerations: The version number consists of three parts: < major >. < minor >. < patch >, namely x.y.z.
In the Greenplum release, the bump of major to major version means that metadata and data are no longer compatible. Users need to upgrade or import and export data that needs to be displayed. The general release frequency is several years in Greenplum. And bump of minor generally includes some feature releases, but it will not cause data incompatibility. Bump of patch is usually a bug fix. We need to consider release candence, especially for major release. After the general version is released, there is a support lifecycle. Therefore, when engineers submit code, they need to submit code to different branches at the same time (such as 5X_STABLE and 6X_STABLE in Greenplum). If there are too many versions released, users need to upgrade frequently, which is another cost. This is also why we need to control the cadence of major version releases. In the previous roadmap discussion email thread, we mentioned a PostgreSQL kernel upgrade in the near future. The planned upgrade to PostgreSQL 15.x will bring a lot of metadata changes to the PostgreSQL kernel upgrade. In Greenplum, major version release was also with the PostgreSQL kernel upgrade. Is it a suitable time to wait until the PG 15.x or PG 16.x kernel upgrade is stable? Welcome to discuss
