{"action":"created","issue":{"url":"https://api.github.com/repos/ansible/community/issues/139","repository_url":"https://api.github.com/repos/ansible/community","labels_url":"https://api.github.com/repos/ansible/community/issues/139/labels{/name}","comments_url":"https://api.github.com/repos/ansible/community/issues/139/comments","events_url":"https://api.github.com/repos/ansible/community/issues/139/events","html_url":"https://github.com/ansible/community/issues/139","id":187163682,"number":139,"title":"More time between new things and deprecating old things","user":{"login":"jbscare","id":10979901,"avatar_url":"https://avatars.githubusercontent.com/u/10979901?v=3","gravatar_id":"","url":"https://api.github.com/users/jbscare","html_url":"https://github.com/jbscare","followers_url":"https://api.github.com/users/jbscare/followers","following_url":"https://api.github.com/users/jbscare/following{/other_user}","gists_url":"https://api.github.com/users/jbscare/gists{/gist_id}","starred_url":"https://api.github.com/users/jbscare/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jbscare/subscriptions","organizations_url":"https://api.github.com/users/jbscare/orgs","repos_url":"https://api.github.com/users/jbscare/repos","events_url":"https://api.github.com/users/jbscare/events{/privacy}","received_events_url":"https://api.github.com/users/jbscare/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":11,"created_at":"2016-11-03T19:14:14Z","updated_at":"2016-11-10T18:44:14Z","closed_at":"2016-11-10T18:44:14Z","body":"If a new thing is introduced in version X, which will deprecate an old thing, it'd be nice to have a standard that the old thing isn't deprecated until version X+1, so that there's at least one version where both old and new things are supported without deprecation warnings."},"comment":{"url":"https://api.github.com/repos/ansible/community/issues/comments/259772378","html_url":"https://github.com/ansible/community/issues/139#issuecomment-259772378","issue_url":"https://api.github.com/repos/ansible/community/issues/139","id":259772378,"user":{"login":"abadger","id":209242,"avatar_url":"https://avatars.githubusercontent.com/u/209242?v=3","gravatar_id":"","url":"https://api.github.com/users/abadger","html_url":"https://github.com/abadger","followers_url":"https://api.github.com/users/abadger/followers","following_url":"https://api.github.com/users/abadger/following{/other_user}","gists_url":"https://api.github.com/users/abadger/gists{/gist_id}","starred_url":"https://api.github.com/users/abadger/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/abadger/subscriptions","organizations_url":"https://api.github.com/users/abadger/orgs","repos_url":"https://api.github.com/users/abadger/repos","events_url":"https://api.github.com/users/abadger/events{/privacy}","received_events_url":"https://api.github.com/users/abadger/received_events","type":"User","site_admin":false},"created_at":"2016-11-10T18:44:14Z","updated_at":"2016-11-10T18:44:14Z","body":"We talked this over and came to two conclusions:\r\n* Having deprecated code without the code emitting a deprecation message isn't a good idea.\r\n* We decided that it doesn't make sense for us to introduce a longer time period between deprecation and removal at this point.\r\n\r\nSo we're not going to change our releases and deprecation message strategy for this.\r\n\r\nHowever, you can get this same effect at your site via the deprecation_warnings config option.  You'll have to be vigilant about managing it, though, so that you don't miss deprecation warnings down the line:\r\n\r\n* When you install a new ansible, set deprecation_warnings=False in ansible.cfg for boxes using that version.\r\n* When you've upgraded previous ansible installations to the new version, set deprecation_warnings=True for boxes using that version.\r\n* Proceed to fix the deprecations in your playbooks at this point.\r\n\r\nIt's important not to forget the second step otherwise you won't get the deprecations and be prompted to fix your playbooks.  Sorry we aren't going to make a change to the deprecation policy but hopefully that will let you adapt your own workflow for this."}}
{"actor":{"display_login":"abadger"}}