Hi > So, it looks like among the largest packaging teams, only the go team, > the gnome team, and the php team have significantly adopted DEP-14. > > Note that this is not a criticism of DEP-14, only an attempt at > providing numbers about DEP-14 adoption.
I have published similar stats before and I ran a large "poll" on this mailing list with subject "DEP-14: Default branch name 'debian/latest' objections?" to find out what the objections are. My take is that a vocal minority with very strong opinions prevent Debian from landing on a default Debian branch name. I believe that if Julien finalizes https://salsa.debian.org/dep-team/deps/-/merge_requests/16 and Raphael approves if (after gauging that the result is reasonable and has enough consensus), and then Raphael follows up with a MR that changes DEP-14 from candidate to accepted, and 20+ DDs +1 it, we could merge it and have a decision. Once we have a decision, Guido is more likely to support making that decision the default in git-buildpackage, and the people who previously migrated from master to debian/master or debian/sid (while the historic DEP-14 suggested them) are more likely to change to the final branch name. With this everything would most likely converge. If we don't finalize DEP-14, the git-buildpackage default 'master' will continue to be the most likely default, as software defaults triumph policy/standard recommendations.
