Reinhard Tartler <siretart@gmail.com> writes: > On Thu, Jun 19, 2025 at 6:59 AM Martin Dosch <martin@mdosch.de> wrote: > >> >> >> Dear all, >> >> how's the go teams stance on tag2upload? As go packages are team >> maintained it would be nice if we have a consensus on this although there >> are many packages which are effectively maintained by one person. >> > > I'm a quite very happy user of dgit, including on packages maintained > within the Debian golang team, and am looking forward to trying out > tag2upload in the future. Me too. I don't think the Go team would need to have a general policy/preference about tag2upload. I find group-specific policies that FORBID some existing common workflow pattern to be counter-productive. It is better to recommend a particular workflow style, but say nothing if other workflows are permitted or not. I think the Go policies are fairly good in this regard. I think it would be useful to add links to dgit to the Go policies. I only found about dgit through use of tag2upload, and only later noticed that several Go packages had been using dgit. I think it helps to be consistent and continue to use dgit for those package, at least for those co-maintainers who care about this consistency. /Simon
Attachment:
signature.asc
Description: PGP signature