Re: Use of 'debian/latest' in Go team as the default branch name
On Fri, Jan 24, 2025 at 9:25 AM Otto Kekäläinen <otto@debian.org> wrote:
>
> Hi!
>
> 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?
>
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.
--
Shengjing Zhu
Reply to: