[pkg-go] Asking upstream to tag repositories

Dmitry Smirnov onlyjob at debian.org
Tue Mar 29 23:59:07 UTC 2016


On Tuesday, 29 March 2016 2:47:58 PM AEDT Alexandre Viau wrote:
> Heh. Actually, it was very easy. My template is two sentences.

Thank you for taking time to educate our upstreams. :)
Great work.

I've been doing that as well with bugs like:

  https://github.com/square/go-jose/issues/83

where you can find my template.

I always try to mention Debian Upstream Guide and include links to resources 
with information about versioning.

In my experience filing those bugs often helps but I've also seens some cases 
of resistance...

IMHO next stage would be to convince upstreams to vendor tagged versions of 
dependencies contrary to prevailing practice of bundling random snapshots of 
"master". There are some royal abusers of this practice like many projects of 
Docker with inconsistent interdependencies responsible for most time 
consuming troubles of building Docker releases...

-- 
Cheers,
 Dmitry Smirnov.

---

The surest way to corrupt a youth is to instruct him to hold in higher
esteem those who think alike than those who think differently.
        -- Friedrich Nietzsche
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.alioth.debian.org/pipermail/pkg-go-maintainers/attachments/20160330/057b1db4/attachment.sig>


More information about the Pkg-go-maintainers mailing list