On Friday, May 23, 2014 2:37:16 PM UTC-5, Rob Reynolds wrote: > > > > > On Fri, May 23, 2014 at 12:00 PM, Kylo Ginsberg > <ky...@puppetlabs.com<javascript:> > > wrote: > >> On Fri, May 23, 2014 at 2:58 AM, Paul Seymour <paul.s...@ig.com<javascript:> >> > wrote: >> >>> >>>> +1 - let's file a bug report. >>>> >>> >>> https://tickets.puppetlabs.com/browse/PUP-2650 >>> >> >> For more context here, puppet has a 'deprecation_warning' method which is >> used for this new message and also in a number of other places. In puppet >> 3.7, we're planning to introduce a number of additional deprecation >> messages (for functionality which will be removed in puppet 4) >> >> So there are at least two possibilities here: >> 1) Make all deprecation messages Info-level rather than Warning-level. So >> you'd need to specify --verbose to see the deprecation messages. >> 2) Leave the deprecation messages at Warning-level, but add a >> 'warn-on-deprecation' setting (possibly with a better name). >> > > How about an ignore-deprecation-warnings setting? This way it's more in > your face at start but once you are familiar with the things going away you > might want to turn it off? It doesn't seem like there is an optimal way of > introducing deprecation warnings without some level of surprise. >
+1 By default, deprecation messages should be warnings, and they should be enabled. It is perfectly reasonable, however, to have an option to turn them off. Or alternatively, perhaps an option to lower (or raise) their severity level. John -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/440e312b-bffc-408c-bad3-bdf45265957a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
