Hi Rob, nice proposal, would definitively help people to deal with the stated problem. Another approach could be to break and deprecate less things.
Sure, I'm just kidding ;-) I love moving things forward. But you know, there's a grain of truth in every joke. We should not forget about the fact that by the end of the day we are talking about a tool designed to manage configuration. For many people right now the configuration manager is the fastest moving target in their tool stack. Your proposal is telling me that we have a cfgmgmt tool struggling with the amount of deprecations it produces. Sad story. We work for the tool, not the other way round. Cheers, Thomas Am 18.03.2016 um 19:12 schrieb Rob Nelson: > Happy Friday, everyone! This morning I had some semi-intelligible > thoughts about feature deprecation in Puppet, specifically because I got > bit with an upgrade issue last night. We do user stories a lot at work, > so I'm going to frame it that way. I was curious what other opinions > people have on this problem and how it can best be addressed. Thanks! -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-dev/ncn1cd%24987%241%40ger.gmane.org. For more options, visit https://groups.google.com/d/optout.
