On 01.11.18 05:23, Dmitry Smirnov wrote: > Why bother? Anything critical fixed? Why not just wait for normal (non-RC) > release?
Well, given that 1.1 has breaking changes and you skipped 1.2, pushing the RC to experimental is good packaging practice. Your choice – if it was my package I'd do it. > IMHO consul should be in sync with Nomad. Once Nomad bumps Consul dependency > I'll be working on packaging of new Consul release. Well, Nomad doesn't have to *depend* on stuff like being able to configure the port used for Serf (1.2.2) or using go-sockaddr templates for join and retry-join (1.1). I for one do need the former (doing it with NAT rules is no fun and somewhat fragile) and could make very good use of the latter, these templates would simplify my Ansible code considerably. There's also new features like native Kubernetes support or weighing SRV records, and bugfixes (like a DNS issue I've already run into) which have been fixed during 1.2. Thus just relying on Nomad's dependency isn't enough. -- -- Matthias Urlichs
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Pkg-go-maintainers mailing list [email protected] https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-go-maintainers
