Go teams stance on tag2upload
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.
Best regards,
Martin
-------- Ursprüngliche Nachricht --------
Von: Ian Jackson <ijackson@chiark.greenend.org.uk>
Gesendet: 19. Juni 2025 10:24:10 UTC
An: debian-devel-announce@lists.debian.org
Betreff: tag2upload is now in open beta
We are pleased to announce that tag2upload is now in open beta.
We think it is suitable for use in the following situations:
* You have your co-maintainers' blessing to try tag2upload.
(Or, the maintainers' blessing, in the case of an NMU.)
* You'll be monitoring the output to check that everything seems in
order, and be prepared to do some rework.
* Be very aware of the freeze! Do not just upload to unstable as
your first test! Uploads to unstable, targeting trixie, *can* be
done with tag2upload - but in most cases you will probably want to
upload the same package to experimental first.
* You should carefully read the primary documentation:
- https://wiki.debian.org/tag2upload
- git-debpush(1)
* You should use the latest git-debpush 13.x from experimental.
Feedback is very welcome.
Thank to our closed beta programmme participants for all the testing
and feedback - especially, thanks to Simon Josefsson and Anton Gladky.
Compared to the previous closed beta:
* We are explicitly inviting participation from folks whose existing
upload flow is not dgit-based. Indeed, these are the users who
we expect to get the most benefit from tag2upload.
* There is no longer any need to contact us to have your package(s)
passlisted. You should still have your co-maintainers' approval!
Ian & Sean.
(tag2upload Delegates)
Reply to: