Hello everyone, On Thu, 11 Sept 2025 at 21:00, Peter Wienemann <[email protected]> wrote: > > merging [0] reminded me of our discussion to change the merge behaviour > for security tools team packages on salsa during DebConf25 (no merge > commits anymore) [1].
Regarding our BoF at DebConf25; I have finished the editing of the recordings and sent it to the video team for processing (opening and closing cover images) and publishing. On Thu, 11 Sept 2025 at 21:46, Simon Josefsson <[email protected]> wrote: > > Peter Wienemann <[email protected]> writes: > > > Hi, > > > > merging [0] reminded me of our discussion to change the merge > > behaviour for security tools team packages on salsa during DebConf25 > > (no merge commits anymore) [1]. > > > > Are there objections to this plan from persons who did not participate > > in the DebConf BoF? > > I also prefer fast forward merges so +1 from me. +1 from me too. > Btw, tag2upload doesn't need any hooks any more. I've uploaded some > pkg-security packages and it works fine. I suggest everyone consider > using 'git-debpush' to release and upload packages. I've also heard good things about debusine, I'd like to also give that a go sometime. > Btw^2, my perception is that DEP14 debian/latest is more common than > debian/unstable, but my view is limited so this may be biased. In case > you want to consider another data point before recommending > debian/unstable as a team policy. I don't like debian/latest as opposed to debian/unstable because it gets confusing when someone wants to upload packages to experimental (debian/latest + debian/experimental), but it's not the end of the world, what matters the most is consistency IMO. Thanks for raising the discussion Peter! -- Samuel Henrique <samueloph>
