Leonid, 2.2.0-incubating was promoted on 3 November. These post-release steps from the Release Runbook are still open. The website part is already in a draft pull request from Dianjin Wang (tuhaihe):
https://github.com/apache/cloudberry-site/pull/413 The review comment on that pull request is: https://github.com/apache/cloudberry-site/pull/413#issuecomment-6644895875 Dianjin can fix the page. He cannot create the missing tags or the GitHub Releases. Those need you. 1. Final release tags. 2.2.0-incubating exists on apache/cloudberry and apache/cloudberry-backup. apache/cloudberry-pxf and apache/cloudberry-go-libs have only the rc1, rc2, and rc3 tags. The PXF RPM/DEB link on the draft page returns 404. 2. GitHub Releases. None yet for 2.2.0 on any of the four repositories. The core and backup tag pages have no .rpm or .deb. The draft page labels those cells as if the binaries are there. Convenience binaries, if we are publishing them, belong here, within a week of the release per the runbook. 3. The signature sample on the draft page is Tue 20 Oct 2026 05:54:30 PM CST. That matches the core tarball only. Backup, go-libs, and PXF were signed on 19 Oct 2026, same key. The page should name the core tarball, or show the other dates. That edit is Dianjin's. 4. Announcement mail. Not sent. From an @apache.org address, To [email protected], Cc [email protected] and [email protected], subject "[ANNOUNCE] Apache Cloudberry (Incubating) 2.2.0 released". The runbook template names cloudberry-backup and cloudberry-pxf. This release also ships cloudberry-go-libs. Best sent after the website pull request is live, so the Download and Changelog links resolve. 5. Incubator status page. https://incubator.apache.org/projects/cloudberry.html has news lines for 2.0.0 and 2.1.0 and none for 2.2.0. That line goes up once the announcement is out. 6. Remove 2.1.0-incubating from dist/release after the website pull request is merged. It is still at https://dist.apache.org/repos/dist/release/incubator/cloudberry/. The live download page still links it at downloads.apache.org, so do not remove it first. 7. Remove the old release candidates from dist/dev. rc1 and rc2 are still there. rc3 was moved to release. The runbook calls this optional. For 2.1.0 it was done the day after promotion. 8. Announcement blog post. The 10 September preview still says 2.2.0 has not been officially released. After this release, the checklist should require the tag and the GitHub Release to exist before a downloads page links them, and a sample signature should match every artifact in the loop or name the one artifact it matches. Thanks, Ed --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
