On 24/01/25 1:39 pm, Shengjing Zhu wrote: > On Fri, Jan 24, 2025 at 9:25 AM Otto Kekäläinen <o...@debian.org> wrote: >> Michael Stapelberg proposed in 2017 that the Go team should use >> 'debian/sid' as the default branch, in effort to unify with DEP-14 at >> the time >> (https://go-team.pages.debian.net/workflow-changes.html#_new_workflow_3). >> >> Turns out using 'sid' as the git HEAD wasn't a good idea, as it may >> lead to flip-fopping between 'debian/sid' and 'debian/experimental' or >> alternatively leading to uploads to experimental from a branch that is >> named 'sid'. Hence in 2020 DEP-14 was updated and clearly recommend >> 'debian/latest' as the primary option now. >> >> >From https://dep-team.pages.debian.net/deps/dep14/: >>> In Debian this means that uploads to unstable and experimental should be >>> prepared either in >>> the debian/latest branch or respectively in the debian/unstable and >>> debian/experimental >>> branches. >> ... >>> The helper tools that do create those repositories should use a command >>> like git symbolic-ref >>> HEAD refs/heads/debian/latest to update HEAD to point to the desired branch. >> >> Can we agree to update the Go team policy to follow this and default >> to 'debian/latest' going forward?
I just feel spending so much time over naming conventions is not worth the effort, and even less so enforcing it so much. Is it really that important? As I asked you in the MR as well, is there an automated way of changing the names of branches? If not, it is not a good idea in my opinion. There are also a lot of packages in the archive which follow master for the main branch. > There are already too many long threads about changing workflow. I > feel it is difficult and there is no time to follow on. I feel > frustrated that someone joined the Go team newly and continuously > proposed changing workflow while I think most existing uploaders are > used to the old workflow. The old one just works. I somewhat agree, though some of the proposed changes are actually useful (like CI) and I really appreciate the effort. I am just hopeful that they are rather just "guidelines" than strict rules that must be followed, as and failure to follow them line by line would result in problems. I’m also finding it problematic that when I raise concerns—like if something seems off—it just gets brushed aside with, "Well, it works for me." If there's continued resistance to uploads like this[1] that I and other are making to the go team, especially when the policy isn't being followed line by line, I’m beginning to think it might be better to move my packages elsewhere and step away from the team entirely. [1] https://lists.debian.org/debian-go/2024/12/msg00116.html Best, Nilesh
