Re: Use of 'debian/latest' in Go team as the default branch name
On Sun, Jan 26, 2025 at 8:16 AM Otto Kekäläinen <otto@debian.org> 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 frustrates me immensely to re-learn aspects of my day-to-day.
> >
> > After noticing workflow fragmentation in the Go packaging team (which I started), I tried fixing this with the workflow
> > changes proposal, but did not succeed in implementing it. The lack of effective automation and slow pace of changes
> > in the surrounding tooling despite my willingness to contribute time and energy killed any motivation I had.
>
You now know that the workflow changes in 2017 causes fragmentation.
Now you start the second fragmentation.
Everytime people try to create a unified workflow to replace the old
ones, it just creates another new one. As others have mentioned,
Debian is not a company, that manager can force a workflow.
--
Shengjing Zhu
Reply to: