Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Roadmap Discussion: Future Direction of cloudberry-backup

Open
#80 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Quiet
Tech stack
go, postgresql
Domain
databases

Research direction

No implementation file, test, or entry point is named. Start by reviewing the current gpbackup and gprestore utilities, incremental backup support, plugins, and gpbackman integration, then summarize concrete community use cases and pain points. Done means the project has agreed priorities for its next development phase.

Written by the indexing model from the issue text.

Description

Background

As the cloudberry-backup project continues to evolve, we want to ensure that our development priorities align with the community's needs. We've recently integrated gpbackman as our open-source backup management tool and are now planning the next phase of development.

Current Status

cloudberry-backup currently provides:

  • gpbackup and gprestore utilities for backup and restore
  • Incremental backup support
  • Plugin support (S3, etc.)
  • gpbackman integration for backup lifecycle management

We Need Your Input!

We'd love to hear from the community:

  1. Missing Features: Are there any critical features we've missed that you need for your backup workflows?

  2. Pain Points: What are the biggest challenges you face with the current backup tools?

Please share your thoughts by:

  • Commenting on this issue with your feedback
  • Sharing your specific use cases or requirements
  • Suggesting additional features or improvements

Related Resources

Thank you for being part of the cloudberry-backup project! Your feedback will directly shape the future of this project. 🙏

Dominant language
Go
Stars
18
Forks
22
Avg merge
21h 31m
Merged PRs (30d)
4

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from apache/cloudberry-backup

All issues in apache/cloudberry-backup

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.