Thanks for preparing RC3!

+1 binding

[x] Download links are valid and accessible. - Ok
[x] GPG signature is valid for the release artifact using the KEYS file. - Ok
[x] SHA512 checksums are correct and verified. - Ok
[x] Source release artifact filename includes "incubating". - Ok
[x] LICENSE, NOTICE, and DISCLAIMER files exist and are accurate. - Ok
[x] No unexpected binary files in the source release. - Ok
[x] All source files have appropriate ASF headers (excluding generated
files and legacy files). - Ok
[x] Build completes successfully from source with clear instructions. - Ok
  Built successfully on Rocky8/9/10, Ubuntu 22.04/24.04

We have addressed the LICENSE-related issues pointed out in RC1 and RC2.

Since we started using LLM-based tools for release reviews, we can
find and fix LICENSE issues much faster and more systematically than
before. While checking RC3 that way, I found a few more places that
can be improved. None of them needs a new RC, so I suggest they go
into the next release:

- Document contrib/pgcrypto/crypt-md5.c (imported from FreeBSD, with
the original beer-ware notice) in LICENSE:
https://github.com/apache/cloudberry/pull/2161
- List the Bison-generated orafce parser in LICENSE, per LEGAL-291:
https://github.com/apache/cloudberry/pull/2162
- Remove a Windows-only setlocale() fallback in PL/Perl that was copied
from Perl's POSIX.xs; it is never compiled on Linux or macOS:
https://github.com/apache/cloudberry/pull/2158

All of these were inherited from PostgreSQL/Greenplum and have shipped
in every earlier release. Getting LICENSE and NOTICE right for a
codebase with this much history (PostgreSQL, Greenplum and a number of
bundled components) is an incremental process, and I don't think we
should expect to finish it in one release. Each round has made the
release noticeably cleaner, and we will keep improving it in the next
releases.

Best,
Dianjin Wang

On Tue, Oct 20, 2026 at 8:28 PM Leonid Borchuk <[email protected]> wrote:
>
> Hi all,
>
> I would like to call a VOTE to release Apache Cloudberry (Incubating) 
> 2.2.0-rc3.
>
> The 2.2.0-rc1 and 2.2.0-rc2 was cancelled because of License issues,
> see details in
> rc1: https://lists.apache.org/thread/xqkkmrp9knfgnoy1pmfcqxobs0m30b5l
> rc2: https://lists.apache.org/thread/cp38o038gc9q5lo930cnhp5ft7qllhxb
>
> The majority of LICENSE fixes have been addressed in rc1, but the most
> insidious ones
> were still waiting for us. Some of these are 21 years old and relate
> to the company's
> founders of Greenplum. I believe we have addressed them too.
>
> ## Release Candidate Artifacts
>
> This vote covers the source release artifacts for Apache Cloudberry
> (Incubating) 2.2.0-rc3,
> including the core Cloudberry project and the components
> cloudberry-backup, cloudberry-pxf and cloudberry-go-libs.
>
> Staged release 
> artifacts:https://dist.apache.org/repos/dist/dev/incubator/cloudberry/2.2.0-incubating-rc3/
>
> Git tag & commit for the release:
> - cloudberry
>  https://github.com/apache/cloudberry/tree/2.2.0-incubating-rc3
>  
> https://github.com/apache/cloudberry/commit/13d3c58eaa0c07afab350dcafbbae7ef610aa862
>
> - cloudberry-backup
>  https://github.com/apache/cloudberry-backup/tree/2.2.0-incubating-rc3
>  
> https://github.com/apache/cloudberry-backup/commit/bd135816570d10cf25ca660f8b13ae887475744b
>
> - cloudberry-pxf
>  https://github.com/apache/cloudberry-pxf/tree/2.2.0-incubating-rc3
>  
> https://github.com/apache/cloudberry-pxf/commit/01c2e00b64166740cabfcae1ceee42a72e520594
>
> - cloudberry-go-libs
>  https://github.com/apache/cloudberry-go-libs/tree/2.2.0-incubating-rc3
>  
> https://github.com/apache/cloudberry-go-libs/commit/c5da03b9a8184c06cfbe828d4c44ad3a3763df20
>
>
> KEYS file:https://downloads.apache.org/incubator/cloudberry/KEYS
>
> GPG signature key: 9397D9D3BAD2B7D474A16671AA15045C6ACA3F2B
>
> The GPG user ID(s): Leonid Borchuk <[email protected]>
>
> ## 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.
> Also, it is helpful to list the items you verified when casting your
> vote in your reply - it shows what you vote for.
>
> [ ] +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
> Oct 24, 2026 at 08:00 UTC.
>
> ## Checklist for reference:
>
> [ ] Download links are valid and accessible.
> [ ] GPG 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.
>
> More detailed checklist, please refer to:
> https://github.com/apache/cloudberry/wiki/Source-Release-Checklist
>
> Build/Install guides (for reference):
> - cloudberry: https://cloudberry.apache.org/docs/deployment/quick-deploy
> - cloudberry-pxf:
> https://github.com/apache/cloudberry-pxf/blob/2.2.0-incubating-rc3/README.md
> - cloudberry-backup:
> https://github.com/apache/cloudberry-backup/blob/2.2.0-incubating-rc3/README.md
> - cloudberry-go-libs:
> https://github.com/apache/cloudberry-go-libs/blob/2.2.0-incubating-rc3/README.md
>
>
> ## GPG Signature and SHA512 checksums Verification Instructions
>
> Please refer to our step-by-step guide:
> https://cloudberry.apache.org/releases/#verifying-releases
>
> ## About Convenience Binaries
>
> After this source release vote passes and the release is published, we
> plan to provide optional
> convenience binaries via GitHub Releases for easier testing. These
> binaries are not part of this
> vote and are not ASF release artifacts.
>
> Thanks for reviewing and voting!
>
> Best,
> Leonid

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to