On Wed, 2024-11-13 at 21:26 +0000, Luca Boccassi wrote: > On Wed, 13 Nov 2024 at 21:20, Ben Hutchings <b...@decadent.org.uk> wrote: > > > > Following the branch renaming in the linux repository and discussion in > > today's team meeting, I want to rename branches in other kernel-team > > package repositories to follow DEP-14. > > > > For iproute2, I plan to rename "debian/sid" to "debian/unstable" and > > the other suite branches to have a "debian/" prefix. > > The only active branch apart from debian/sid is > debian/bookworm-backports, which already has the prefix. If you want > to duplicate the stale branches to add debian/ prefix there that > sounds fine, but it's unlikely they are going to see any activity, > doesn't hurt I guess, branches are cheap, and the debian/ prefix makes > sense to namespace them, so not a problem. > However, I'm not sure about sid -> unstable? What's the reason for > that? It's a lot of churn to change everything and everyone given it's > the main branch where I merge things and do all the work?
The reason is that DEP-14 specifically mentions "debian/unstable" instead of "debian/sid", so that's what other developers are going to expect to see. I realise all this renaming will be disruptive, but it moves us toward a more consistent experience for developers working across the kernel team packages and across the whole distribution. Ben. -- Ben Hutchings One of the nice things about standards is that there are so many of them.
signature.asc
Description: This is a digitally signed message part
