Hi all,
Regarding the sandbox files in the bootcamp, I plan to move them to
the `deploy/sandbox` directory. I also plan to refactor them to use
the Cloudberry build image as the builder. This will help us avoid
maintaining duplicate base image Docker files across multiple
directories.
BTW, do we
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
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
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
Hi all,
Over the past two years, the bootcamp repo has grown to include
various types of content, such as sandbox Dockerfiles, tutorials, and
learning materials. I’d like to start a discussion around reorganizing
the `apache/cloudberry-bootcamp` repo to improve clarity and
maintainability across o
