Re: [DISCUSS] Reorganizing the `apache/cloudberry-bootcamp` repo

2025-06-09 Thread Dianjin Wang
Cool! Then I need to rethink the way how to reorganize the `cloudberry-bootcamp` better after our `cloudberry-devops-release` move to the main repo. Best, Dianjin Wang On Mon, Jun 9, 2025 at 5:25 PM Ed Espino wrote: > > Hi Leonid, > > Totally agree — let’s move the build scripts into the main r

Re: [VOTE] Release Apache Cloudberry (Incubating) 2.0.0-rc1

2025-06-09 Thread Kent Yao
H Ed, Do you mean that ce1fc9438989ac22146c1c7e483933f3560e6572 is not the final hashtag if RC1 passes, and there will be new commits to replace 2.0.0-incubating-rc1 with 2.0.0-incubating in the source release? If so, the checksum verification step here becomes a variable. Kent Dianjin Wang 于20

Re: [DISCUSS] Reorganizing the `apache/cloudberry-bootcamp` repo

2025-06-09 Thread Ed Espino
Hi Leonid, Totally agree — let’s move the build scripts into the main repo. Having everything in one place will simplify development, especially for larger changes like PAX support. It’ll streamline testing, reduce cross-repo friction, and make iteration much faster. We can always revisit a split

Re: [VOTE] Release Apache Cloudberry (Incubating) 2.0.0-rc1

2025-06-09 Thread Kent Yao
Hi Ed, This file name appears to be a fair use to me, as it doesn't cause any confusion with branding-related items, such as product names or domain names. (This is not my area, though) Bests, Kent Ed Espino 于2025年6月9日周一 16:47写道: > Hi Kent, > > While I have you — I’d also appreciate your tho

Re: [VOTE] Release Apache Cloudberry (Incubating) 2.0.0-rc1

2025-06-09 Thread Ed Espino
Hi Kent, You’re absolutely right — I’ve now confirmed that the internal version string does include -rc1. That suffix should only exist in the artifact name and Git tag, not in the version metadata of the release itself. This means RC1 is invalid from a release policy standpoint, and I’ll need to

Re: [VOTE] Release Apache Cloudberry (Incubating) 2.0.0-rc1

2025-06-09 Thread Ed Espino
Hi Kent, While I have you — I’d also appreciate your thoughts on a related concern we discovered during the RC1 review. The source release currently includes a script named greenplum_path.sh, which is generated by gpMgmt/bin/generate-greenplum-path.sh during installation. These filenames contain

Re: [DISCUSS] Reorganizing the `apache/cloudberry-bootcamp` repo

2025-06-09 Thread Leonid Borchuk
I totally agree. It would be great to have a single library where all of our assets are stored. But until we start large-scale reconstruction work, I would like to ask a slightly off-topic question: Why do we even need a cloudberry-release-devops? Why can't all our scripts be stored in the main re