Re: Branching for experimental uploads on Salsa?
Hi Cory,
On 2025-06-20 06:29, Cordell Bloor wrote:
> My default would be to do my work in a short-lived branch named
> 'experimental' and then merge it into 'master' once Debian Trixie is
> released. [...] The main reason for creating this separate branch for
> experimental would be to avoid having to back out changes from 'master'
> if minimal fixes are required to the package on Unstable/Testing for
> Trixie to address an RC bug.
This is the standard practice.
We've never followed it because our packages aren't "at risk" of such
breakages that much I guess, but that's the only proper way to do it.
Speaking of, wev've also never followed DEP-14 for branch names [1]
which I like, but I don't want to force them onto anyone.
> 'd like to make uploads to experimental for a few packages with ROCm
> 6.4 updates (e.g., rocminfo, rocm-smi
Just so we don't duplicate any work, I've been looking into some
pkg-rocm-tools features for which I'll eventually be updating rocrand
and hipsolver to 6.4 (my typical test balloons).
Best,
Christian
[1]: https://dep-team.pages.debian.net/deps/dep14/
Reply to: