On 24 October 2016 at 19:01, Erik Dalén <erik.gustav.da...@gmail.com> wrote:
> As an aside we recently got nailed when puppetlabs-ntp became no >> longer puppet3 compatible on master prior to the new version being >> released. As operators and developers, these incompatible transitions >> really need to be well thought out on their impact. I can't count the >> number of times we've been hit when someone decided to change their >> gem (or ruby) dependencies mid release cycle and it breaks everything >> even if we don't actually consume any code from that module. Sorry >> it's a major pet peeve of mine when we have to drop everything and go >> figure out who's doing breaking changes mid cycle and either pin or >> find a work around because of backwards incompatibilities. >> > > This sounds like you want a stable environment but yet you are tracking > master for your dependencies. > Just wait with upgrading until you have time to do it instead of all the > time :) > I can't emphasize enough how helpful folks running master are. For example Dominic Cleal, of Foreman fame, found and reported a number of embarrassing slips on our side over the years before they were released and could impact the wider community. Regards, David -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-dev/CALF7fHYW_MpGfEb9P54iYdPri5DeFM9fz8MjbmZ%3DyaJEQXpGEg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
