Re: Use of 'debian/latest' in Go team as the default branch name

2025-02-05 Thread Otto Kekäläinen
Hi! Thanks Arnaud for a thoughtful reply. The list of top contributors is a great data point!

Re: Use of 'debian/latest' in Go team as the default branch name

2025-02-05 Thread Arnaud Rebillout
Hello again, sorry for the previous email, seems that formatting was a disaster, let me try again. On 26/01/2025 07:15, Otto Kekäläinen wrote: > What comes to DEP-14 and timelines, do you agree that debian/sid > predated the 2020 version of DEP-14 and the two options it now > recommends are debia

Re: Use of 'debian/latest' in Go team as the default branch name

2025-02-05 Thread Arnaud Rebillout
Hello Otto, On 26/01/2025 07:15, Otto Kekäläinen wrote: > What comes to DEP-14 and timelines, do you agree that debian/sid > predated > the 2020 version of DEP-14 and the two options it now > recommends are debian/latest and is some situations debian/unstable? That is correct, and I didn't get th

Re: Use of 'debian/latest' in Go team as the default branch name

2025-01-27 Thread Otto Kekäläinen
Hi! Thanks Tina for following up on the mailing list! > > Can we agree to update the Go team policy to follow this and default > > to 'debian/latest' going forward? > > I strongly oppose this: not only it would create an enormous amount of > churn, but it is also a regression as many have already

Re: Use of 'debian/latest' in Go team as the default branch name

2025-01-26 Thread Simon Josefsson
Martina Ferrari writes: > 1. Recommends `wrap-and-sort -tsa`, along with changes in default > settings for dh-make-golang. Do you have anything against 'wrap-and-sort 'satbk'? I believe for most cases it results in the same output, but it does result in predictable binary package sort order (ex

Re: Use of 'debian/latest' in Go team as the default branch name

2025-01-26 Thread Martina Ferrari
Hi, On 24/01/2025 01:24, Otto Kekäläinen 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). I feel it is important to h

Re: Use of 'debian/latest' in Go team as the default branch name

2025-01-25 Thread Shengjing Zhu
On Sun, Jan 26, 2025 at 8:16 AM Otto Kekäläinen wrote: > To quote https://michael.stapelberg.ch/posts/2019-03-10-debian-winding-down/ > > > Personally, I cannot keep enough details of the different workflows in my > > head. Every time I touch a package that > > works differently than mine, it fru

Re: Use of 'debian/latest' in Go team as the default branch name

2025-01-25 Thread Otto Kekäläinen
Hi Arnaud and Mathias! > 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 gener

Re: Use of 'debian/latest' in Go team as the default branch name

2025-01-25 Thread Nilesh Patra
On 26/01/25 1:30 am, Mathias Gibbens wrote: > From most of what I've seen Otto propose, it seems that he's wanting > to push for use of more modern software engineering practices like you > might find at a good software engineering company. I think that's a > commendable goal, That's my impressi

Re: Use of 'debian/latest' in Go team as the default branch name

2025-01-25 Thread Mathias Gibbens
On Thu, 2025-01-23 at 17:24 -0800, Otto Kekäläinen wrote: > Can we agree to update the Go team policy to follow this and default > to 'debian/latest' going forward? I'll prefix this with a disclaimer that I haven't fully followed the discussion on proposed workflow changes the past several month

Re: Use of 'debian/latest' in Go team as the default branch name

2025-01-24 Thread Arnaud Rebillout
On 24/01/2025 08:24, Otto Kekäläinen wrote: 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

Re: Use of 'debian/latest' in Go team as the default branch name

2025-01-24 Thread Nilesh Patra
On 24/01/25 1:39 pm, Shengjing Zhu wrote: > On Fri, Jan 24, 2025 at 9:25 AM Otto Kekäläinen 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-

Re: Use of 'debian/latest' in Go team as the default branch name

2025-01-24 Thread Simon Josefsson
Otto Kekäläinen writes: > 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 gen

Re: Use of 'debian/latest' in Go team as the default branch name

2025-01-24 Thread Shengjing Zhu
On Fri, Jan 24, 2025 at 9:25 AM Otto Kekäläinen 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). > > Tur

Use of 'debian/latest' in Go team as the default branch name

2025-01-23 Thread Otto Kekäläinen
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