GitHub user my-ship-it created a discussion: [DISCUSS] Where should topic branches live: apache/cloudberry or personal forks?
> This is a pointer to a thread on [email protected]. Please reply on > the mailing list so the discussion stays in one place: > https://lists.apache.org/thread/89jhpr74ck9nq486h8c9vdm4sth6y2cp > > Not subscribed? Send an empty email to [email protected], > or reply from the archive page above after signing in with your Apache ID. **Summary** [apache/cloudberry](https://github.com/apache/cloudberry/branches/active) has 21 branches today. Besides `main` and the release branches, most were created for a single PR (`fix_issue_1915`, `cp_CVE_2025_12817`, `bp_old_main`, `reshke-patch-1`, ...), and some names don't say what the branch is for at all (`ijjdiew`, `PG_`). The proposal: 1. The main repo keeps `main`, `REL_*_STABLE`, archive branches, and shared `feature/*` branches for multi-person work agreed on dev@. 2. Everything else (bug fixes, single-author features, cherry-picks, backports) goes in personal forks. 3. One-time cleanup: owners have two weeks to claim branches they still need; the rest get deleted. PR history stays in `refs/pull/*`. **If you own one of the current branches** and still need it, please say so on the thread. GitHub link: https://github.com/apache/cloudberry/discussions/2157 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
