On Fri, 03 Aug 2018 at 08:21:28 +0200, W. Martin Borgert wrote: > In fact, I thought that "upstream/master" were DEP-14-ish, but > only "upstream/latest" (for the newest release) is.
Yes. The simple case for DEP-14 is that you are only following one upstream branch, which is upstream/latest; the more complex case is that you are also following an upstream stable-branch or something, for which naming like upstream/1.2.x is suggested for the older (stable) branch. dbus <https://salsa.debian.org/utopia-team/dbus/branches> and glib2.0 <https://salsa.debian.org/gnome-team/glib/branches> are examples of DEP-14 packages that track more than one upstream branch. There is no upstream/master, upstream/unstable, upstream/stretch or similar in DEP-14, because: * if uploads to a particular Debian suite are tracking upstream versions older than the latest, they presumably meet some sort of criteria for which versions are acceptable, most commonly "is from the same stable-branch as the previous release"; the branch is named after those criteria rather than the target suite, because multiple suites might be sharing an upstream release series * if there is no upstream version that is acceptable for e.g. stable, then new upstream versions won't get imported for that suite, so there's no need to maintain a branch that they could be imported into (if using pristine-tar, it uses commits, not branches, to check out upstream source) smcv
