Jira (PUP-2650) 3.6.1 issues "warning" message for deprecation

[Andy Parker (JIRA)]

Title: Message Title

Andy Parker commented on an issue   Re: 3.6.1 issues "warning" message for deprecation Dominic Cleal, I mostly agree with you, but we put in the message because it turned out that when we did change the behavior of the rpm provider some users got caught by surprise. Jo Rhett, I understand your frustration with the log spam, but I don't agree that this is an invalid means of communicating changes. There isn't anything I can do about the past versions, but you'll be able to turn off these messages going forward. The reason that I avoid relying only on release notes is because I know myself and I know what I've seen from others. For the most part, people don't read the documentation when trying to update software. Usually what ends up happening is that they try to update, all sorts of things that they never anticipated stop working, they fight with it for a while, and then they give up and never update. Given the number of changes, some subtle, some not so subtle, that we are building up for puppet 4, I think that having everyone read release notes, do a review of every way that they are using puppet, making changes, and hope that it will now work on the new version isn't a very reasonable expectation. This lead us, and me, to put in warnings to inform users when they are doing something that will be going away or changing. So why have them turned on by default? I want users to upgrade. I want them to be using the newest features and giving feedback. I don't want users waiting until the last moment to try to rid themselves of all of the old features that they were using. In order to do this we have puppet issue the deprecation warnings by default so that everyone knows what is changing. We often have the deprecation warning point to more information, when the message itself won't provide enough. We have feature flags to enable the new behavior so that users can use it and get off of the deprecated functionality. Finally we are working to make sure the the largest changes between major versions are mostly about just removing deprecated functionality and removing feature flags. Add Comment   Puppet / PUP-2650 3.6.1 issues "warning" message for deprecation Message is issued from agent runs at the warning level for a deprecation message. Warning: The package type's allow_virtual parameter will be changing its default value from false to true in a future release. If you do not want to allow virtual packages, please explicitly set allow_virtual to false. (at /usr/lib/ruby/site_ruby/1.8/puppet/type.rb:816:in... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.