On Sun, 30 Aug 2020 at 15:36:53 +0200, Raphael Hertzog wrote:
> If I know that the next upstream release
> breaks backwards compatitibly and that it will have to mature a long time
> in experimental until all other packages are ready, I might start to
> package it rigth now in debian/experimental and continue to use
> debian/latest for my unstable uploads.
If that's your workflow (the same as src:dbus, where versions 1.13.x
are a development branch not recommended for general use), then I don't
think debian/latest is a good name for that branch, and I'd recommend
using debian/unstable for your unstable uploads.
Rationale: it seems very confusing if a branch with "latest" in its name
does not contain the newest available version :-)
(debian/master didn't have that problem because it's named by analogy
to the "master" branch used in upstream git repositories, which doesn't
really have a fixed meaning anyway.)
smcv
