Can we agree to update the Go team policy to follow this and default to 'debian/latest' going forward? There are <2000 packages in Debian that use the 'debian/sid' branch name, and out of these ~1300 are from the Go team. The Go team should not diverge from general Debian practices unless there is a proper cause. The current situation is only due to historical reasons.
I have to disagree with how you frame it. debian/latest is NOT "general Debian practices". It's merely one of the possible default branch names that is proposed in DEP-14, and it's not widely used in Debian at the moment [1]. As we can see on debian-devel [2], lots of push back and different opinions on what's the best name for the packaging branch.
And as far as DEP-14 goes, debian/sid is a very valid name, so
the Go team is already following DEP-14 best practices here.
Therefore I object to changing the default branch name at this
moment. If a project-wide consensus emerges in the future, we
might revisit this discussion.
And I also suggest reverting the changes you made to the Go team
workflow page [3] [4], right now it reads like this:
> the
recommended Debian packaging branch became debian/latest,
and the upstream
import branch became upstream/latest. The Go team
should align with the latest
DEP-14 recommendations.
It's difficult to have a peaceful discussion when the change being discussed was pushed out on the team already.
Thanks for your time and efforts in driving progress in Debian,
Best,
Arnaud
--
[1] I don't have numbers regarding the packaging branch names in
use, would be nice if someone has it
[2] "DEP-14: Default branch name 'debian/latest' objections?" on debian-devel
[3] https://salsa.debian.org/go-team/go-team.pages.debian.net/-/merge_requests/7
[4] https://go-team.pages.debian.net/workflow-changes.html