Updates:
- The repo `apache/cloudberry-gpbackup` has been renamed to
`apache/cloudberry-backup`; the repo
`apache/cloudberry-gpbackup-s3-plugin` has been archived, and its core
source files have also been migrated to `apache/cloudberry-backup`
(See working branch -
https://github.com/apache/cloudberry-backup/tree/sync-with-upstream).

Now the working branch should have caught up with the achieved GP
versions. For the next step, let's archive the old main branch and
make the working branch the main. Also, we need more tests and update
the ci for it.



On Wed, Sep 24, 2025 at 8:00 AM Dianjin Wang <[email protected]> wrote:
>
> Hi all,
>
> I created an Infra ticket on renaming and archiving the repos:
> https://issues.apache.org/jira/browse/INFRA-27268
>
> Best,
> Dianjin Wang
>
> On Fri, Sep 12, 2025 at 10:33 AM Max Yang <[email protected]> wrote:
> >
> > Thanks for initiating this discussion and providing a clear background on
> > the current state of our backup tooling repositories.
> >
> > 1. Repository Renaming
> >
> > It makes sense to me that renaming apache/cloudberry-gpbackup to
> > apache/cloudberry-backup. The proposed name better aligns with Cloudberry’s
> > independence. This change will also help avoid confusion among users and
> > contributors.
> >
> > 2. Repository Consolidation
> >
> > This simplification will reduce maintenance overhead, improve code cohesion,
> > and make it easier to manage and build an integrated backup ecosystem. The
> > minimal
> > changes in the S3 plugin repository make this consolidation
> > straightforward, and
> > any necessary code adjustments can be handled as part of the merge.
> >
> > Additionally, I support archiving or removing the `original
> > apache/gpbackup-s3-plugin`
> > repository after the consolidation, as it no longer serves a purpose for
> > Cloudberry.
> >
> >
> > Best regards, Max Yang
> >
> >
> > On Thu, Sep 11, 2025 at 8:22 PM Dianjin Wang <[email protected]> wrote:
> > >
> > > Hi all,
> > >
> > > I’d like to open a discussion regarding the repositories related to
> > > our backup tooling.
> > >
> > > ## Background
> > >
> > > We have been cherry-picking commits from Greenplum’s archived gpbackup
> > > into our current repository `apache/cloudberry-gpbackup`. The work has
> > > been carried out in the branch `sync-with-upstream` and is mostly
> > > complete. For details, please see:
> > > https://github.com/apache/cloudberry-gpbackup/issues/46
> > >
> > > ## Topics for discussion
> > >
> > > 1. Repository renaming
> > >
> > > The current repository name is `apache/cloudberry-gpbackup`. Since the
> > > prefix `gp` may imply a dependency on Greenplum rather than Cloudberry
> > > itself, I propose renaming it to `apache/cloudberry-backup`, which
> > > would better reflect the independence of our project.
> > >
> > > 2. Repository consolidation
> > >
> > > There is also a small repository
> > > `apache/cloudberry-gpbackup-s3-plugin`. This repo has seen very few
> > > changes, and its core consists of fewer than 10 files. To reduce our
> > > maintenance and governance overhead, I propose merging it into the
> > > existing `apache/cloudberry-backup/plugins/` directory.
> > >
> > > * This would simplify our repo structure, improve maintainability, and
> > > make it easier to build an integrated backup ecosystem.
> > > * Some code adjustments may be needed to align the plugin more closely
> > > with the main backup tool.
> > > * Since the original `apache/gpbackup-s3-plugin` repo has no important
> > > Cloudberry-specific changes, we can also request the ASF Infra team to
> > > directly remove it after the consolidation.
> > >
> > > ## Next steps
> > >
> > > Before moving forward, I’d like to hear your thoughts and feedback
> > regarding:
> > >
> > > * The proposed renaming of `apache/cloudberry-gpbackup` ~>
> > > `apache/cloudberry-backup`
> > > * The consolidation of `apache/cloudberry-gpbackup-s3-plugin` into the
> > > main backup repo, and deletion of the original
> > > `apache/gpbackup-s3-plugin`
> > >
> > > Looking forward to your input.
> > >
> > > Best,
> > > Dianjin Wang
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: [email protected]
> > > For additional commands, e-mail: [email protected]

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

Reply via email to