[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Suite branches



Hi again,

I opened a MR at [1] with a proposal for an initial implementation of debcargo-conf namespaces. By namespace I mean an identifier for a set of branches which must talk to each other, like the master and pending branches currently do for unstable/exp. The intention is of course to use these for suite branches. Each suite should have its own namespace.

The reason why I introduced a new configuration file (.dcc.conf) is we should have a per-branch source of truth for the branch naming scheme, so all scripts can use it. In theory one could compute the branch names from the current one's (e.g. if the current branch is master (resp. trixie/master) then the pending-release branches are called pending-* (resp. trixie/pending-*), and vice-versa). In practice

1. the computation should still be centralized, i.e. provided by a single function to be sourced by the scripts instead of left to them, at which point one can as well hardcode the names,

2. by harcoding the names we won't have to care about what we call the branches: we'll have the master ones and those managed by the scripts (like the pending release branches), and will still be able to name extra branches as we like.

I am not married to any of the ideas in the MR so please feel free to critique them and/or propose alternatives. Whatever works for keeping suites separate is fine.


[1] https://salsa.debian.org/rust-team/debcargo-conf/-/merge_requests/894


Reply to: