#2157 [DISCUSS] Where should topic branches live: apache/cloudberry or personal forks? New discussion created by my-ship-it

This is a pointer to a thread on dev@cloudberry.apache.org. 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 dev-subscribe@cloudberry.apache.org, or reply from the archive page above after signing in with your Apache ID.

Summary apache/cloudberry 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. apache/cloudberry