-1 (binding) — from the Release Manager
As the release manager for Apache Cloudberry (Incubating) 2.0.0 RC1, I am
casting a binding -1 due to two release-blocking issues identified during
RC review and platform testing.
What’s been verified:
-
Signatures and SHA512 checksums validate correctly
-
LICENSE, NOTICE, and DISCLAIMER files are present and appropriate
-
No binary or compiled artifacts are bundled in the source release
-
Apache RAT executed successfully using Maven (used only for license
audit)
-
Functional testing and CLI output behave as expected
-
Build tested successfully across the following platforms:
-
Rocky Linux 9
-
Ubuntu 22.04 LTS
-
Amazon Linux 2023
-
openSUSE Leap 15.5
Blocking Issue 1: Trademark Compliance – greenplum_path.sh and
generate-greenplum-path.sh
The source release includes a user-visible script named greenplum_path.sh,
which is generated by gpMgmt/bin/generate-greenplum-path.sh during
installation. These filenames include the Greenplum trademark (owned by
Broadcom Inc.) and are active parts of the install process.
ASF policy prohibits the use of third-party trademarks in filenames or
output unless clearly justified and disclaimed. These files may imply
affiliation or endorsement, which is not permitted.
This issue is tracked at:
https://github.com/apache/cloudberry/issues/1149
Blocking Issue 2: Build Failure with --enable-pax
When building with the --enable-pax configuration option, the build fails
if the protobuf development environment is not available. The failure is
not detected during configure, and this leads to an unclear build
experience.
This issue is tracked at:
https://github.com/apache/cloudberry/issues/1148
Next Steps:
I will re-roll RC2 once:
-
These two issues are resolved
-
Installer and build behavior is confirmed across tested platforms
-
Community consensus has been reached
Request for community input:
Before I proceed with RC2, I welcome feedback from PMC members and
contributors:
-
Do you agree that the trademarked filenames must be renamed for
compliance?
-
Are there any other considerations we should account for before
preparing RC2?
Thank you all for your continued review and support. Apologies again for
not catching these issues earlier in the process.
-=e
(Release Manager, Apache Cloudberry (Incubating))
On Fri, Jun 6, 2025 at 12:59 AM Ed Espino <esp...@apache.org> wrote:
> Hi all,
>
> I would like to call a VOTE to release Apache Cloudberry (Incubating)
> 2.0.0-rc1 — the first official Apache release since the project entered
> incubation.
>
> While the community has produced releases prior to joining the Apache
> Software Foundation, this is our first release under the ASF's governance,
> following the official Apache release process and incorporating all relevant
> legal, licensing, and distribution requirements.
>
> ---
>
> Release Candidate Artifacts
>
> Staged release
> artifacts:https://dist.apache.org/repos/dist/dev/incubator/cloudberry/2.0.0-incubating-rc1/
>
> Git tag:https://github.com/apache/cloudberry/releases/tag/2.0.0-incubating-rc1
>
> Commit:https://github.com/apache/cloudberry/commit/ce1fc9438989ac22146c1c7e483933f3560e6572
>
> PGP signature key:
> 3B90B5634E4506F05BA51F2FC9604135C07CD12A — Ed Espino (esp...@apache.org)
>
> KEYS file:https://dist.apache.org/repos/dist/dev/incubator/cloudberry/KEYS
>
> How to Vote
> Please review the release and cast your vote below. If you are a PPMC member,
> please indicate whether your vote is binding.
>
> [ ] +1 Approve the release
> [ ] 0 No opinion
> [ ] -1 Disapprove (please explain why)
>
> The vote is open for at least 72 hours and will close no earlier than June 8,
> 2025 at 08:00 UTC.
>
> Checklist for reference:
>
> [ ] Download links are valid and accessible.
> [ ] PGP signature is valid for the release artifact using the KEYS file.
> [ ] SHA512 checksums are correct and verified.
> [ ] Source release artifact filename includes "incubating".
> [ ] LICENSE, NOTICE, and DISCLAIMER files exist and are accurate.
> [ ] No unexpected binary files in the source release.
> [ ] All source files have appropriate ASF headers (excluding generated files
> and legacy files).
> [ ] Build completes successfully from source with clear instructions.
>
> PGP Signature and SHA512 checksums Verification Instructions
>
> Please refer to our step-by-step
> guide:https://github.com/apache/cloudberry/wiki/Apache-PGP-Signature-and-SHA512-Checksum-Verification
>
> About Convenience Binaries
>
> As this is our initial release under the Apache Software Foundation, we are
> not providing any convenience binaries (such as .rpm, .deb, or Docker images)
> as part of this vote. The official release consists solely of the source
> artifacts linked above.
>
> We will be gathering input from the development community on which
> convenience binaries would be most useful and plan to make them available in
> the near future via appropriate non-release channels.
>
> Please note: any such convenience binaries will not be official ASF releases
> and will be clearly labeled as such, in accordance with ASF policy.
>
> ---
>
> Thanks for reviewing and voting!
>
> Best,
> -=Ed Espino
> (on behalf of the Apache Cloudberry (Incubating) community)
>
> ---
>
> Note: follow ASF release policy and Incubator guidelines:
> https://incubator.apache.org/guides/releasemanagement.html
>
>
> --
> Ed Espino
> Apache Cloudberry (Incubating) & MADlib
>
