I made the change to golang-golang-x-text too, and uploaded it. This is systematic across most Go packages. Is there anyone who think that debian/gbp.conf should NOT contain the relevant 'upstream-vcs-tag' label? I'm wondering if we should use it for all Go packages. Right now I think it is only used in a smaller minority of packages, at least I rarely seems to notice it in existing packages. It is possible to make reasonable arguments against (e.g., it move things further away from a tarball-centric upstream view), but I'm not sure if anyone feels strongly about it. Otto has posted good argument for using it. If we make a decision, it would be nice to improve tooling somehow to notice lack of it. Right now none of the QA tools I use even suggests anything about this. I don't care either way, although if I was forced to chose I would use it, but I do care for consistency since eventually common idioms and patterns save everyone time. So I would be happier if we use it for all packages, or for no packages. Maybe this should be implicit through DEP14. It may be that we are essentially stuck on reaching any form of agreement, though, and things continue to be per-package tradition. /Simon
Attachment:
signature.asc
Description: PGP signature