PXF 2.1 Release with Apache Cloudberry 2.1

[tuhaihe]

We are currently preparing the Apache Cloudberry 2.1 release. As part of this effort, I would like to start a discussion about how we should handle the PXF 2.1 release.

Background

To simplify the release process and reduce overhead, I propose to ship PXF 2.1 together with Cloudberry 2.1 for the upcoming community voting, instead of running an independent PXF release process.

Concretely:

• PXF 2.1 will be branched from the current main branch.
• The branch will be used as the basis for the PXF 2.1 release.
• This avoids running a standalone PXF release workflow, which can be relatively heavy for the community at this stage.

Rationale

• Aligning component releases with the Cloudberry release is a common practice in other incubating Apache projects.
• It reduces release management overhead and coordination cost.
• It provides users with a consistent and tested stack (Cloudberry + PXF) for 2.1.

Feedback and suggestions are very welcome.