{"action":"created","issue":{"url":"https://api.github.com/repos/guard/listen/issues/374","repository_url":"https://api.github.com/repos/guard/listen","labels_url":"https://api.github.com/repos/guard/listen/issues/374/labels{/name}","comments_url":"https://api.github.com/repos/guard/listen/issues/374/comments","events_url":"https://api.github.com/repos/guard/listen/issues/374/events","html_url":"https://github.com/guard/listen/issues/374","id":150641378,"number":374,"title":"Problems with current Ruby Dependency","user":{"login":"bastelfreak","id":341866,"avatar_url":"https://avatars.githubusercontent.com/u/341866?v=3","gravatar_id":"","url":"https://api.github.com/users/bastelfreak","html_url":"https://github.com/bastelfreak","followers_url":"https://api.github.com/users/bastelfreak/followers","following_url":"https://api.github.com/users/bastelfreak/following{/other_user}","gists_url":"https://api.github.com/users/bastelfreak/gists{/gist_id}","starred_url":"https://api.github.com/users/bastelfreak/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/bastelfreak/subscriptions","organizations_url":"https://api.github.com/users/bastelfreak/orgs","repos_url":"https://api.github.com/users/bastelfreak/repos","events_url":"https://api.github.com/users/bastelfreak/events{/privacy}","received_events_url":"https://api.github.com/users/bastelfreak/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/guard/listen/labels/Waiting%20for%20user","name":"Waiting for user","color":"d7e102"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":5,"created_at":"2016-04-24T08:46:28Z","updated_at":"2016-04-24T23:01:39Z","closed_at":null,"body":"Hi,\r\n\r\nlisten 3.0.6 needed at least Ruby1.9.3, you bumped the Ruby version to at least 2.2 in listen3.1.0. This is a major change in my opinion and will break many current setups, and is probably not compatible with semantic versioning. Could you please revoke the latest release or release a new 3.X that has no dependency on a newer ruby?\r\n\r\nPlease don't get me wrong, I really really love new software. But please require ruby2.2 after a major bump of listen, in a 4.X release."},"comment":{"url":"https://api.github.com/repos/guard/listen/issues/comments/214059298","html_url":"https://github.com/guard/listen/issues/374#issuecomment-214059298","issue_url":"https://api.github.com/repos/guard/listen/issues/374","id":214059298,"user":{"login":"e2","id":150197,"avatar_url":"https://avatars.githubusercontent.com/u/150197?v=3","gravatar_id":"","url":"https://api.github.com/users/e2","html_url":"https://github.com/e2","followers_url":"https://api.github.com/users/e2/followers","following_url":"https://api.github.com/users/e2/following{/other_user}","gists_url":"https://api.github.com/users/e2/gists{/gist_id}","starred_url":"https://api.github.com/users/e2/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/e2/subscriptions","organizations_url":"https://api.github.com/users/e2/orgs","repos_url":"https://api.github.com/users/e2/repos","events_url":"https://api.github.com/users/e2/events{/privacy}","received_events_url":"https://api.github.com/users/e2/received_events","type":"User","site_admin":false},"created_at":"2016-04-24T23:01:39Z","updated_at":"2016-04-24T23:01:39Z","body":"@bastelfreak - you didn't fully read my reply. :(\r\n\r\n1. I posted a link to your failed run (as an update to my comment - if you only read a GitHub email notification from me, you didn't get it)\r\n\r\n2. I know about the puppet modules - that's how I found the failing build log. \r\n\r\n3. The error is \"works as expected\". So it is not a RubyGems issue. RubyGems is working correctly by refusing the install the gem.\r\n\r\n4. Yes, I read that semver issue previously. There are cases where this is complex. But here, a shift from 1.9.2 to 2.2 (or 2.3 even) is MUCH smaller than from Ruby 1.8.7 to 1.9.2. (Ask Matz if you're in doubt). Originally, Ruby 1.9 was technically 2.0, but it was named 1.9 to promote migration.\r\n\r\nTo avoid exactly the problem you brought up here: avoiding to upgrade based on version number instead of based on actual changes and impact.\r\n\r\n5. The following is incorrect: \r\n\r\n> The update from listen3.0.6 to 3.1 will break the system if you're on an older ruby version because it fails to install (ok maybe not completely break but you get into some trouble). \r\n\r\nNo, it won't \"break the system\" (a vague term), it will only break PROVISIONING. And this is devops responsibility. If provisioning breaks, that's great, because the services are protected due to a rollback.\r\n\r\nAnd provisioning for devops is \"business as usual\". The point of devops is to isolate such failures as part of creating a deployment plan.\r\n\r\n6. Also, ...\r\n\r\n> Nevertheless, speaking from an Ops perspective: a major update of any software is always itchy\r\n\r\n\"itchy\" is not a specific/technical term compared to the points I gave above.\r\n\r\n> and in the case of ruby not always possible. \r\n\r\nPackaging problem. That's devops responsibility (or the provider of the distro/OS). Not an internal dependency problem that should be fixed here.\r\n\r\n> The ruby bump in the listen gem may be correct in the sense of semver, but it will have a huge impact on productive systems. \r\n\r\nI have yet to hear about ANY specific compelling example that actually occurred. (Or that could occur). And when I say **specific**, I mean that.\r\n\r\n> This is a thing that most people don't expect on a minor change.\r\n\r\nI \"expect\" people to read Release notes and changelogs before upgrading software. And, I have yet to see an example of what \"harm\" I've done to people who upgraded without reading.\r\n\r\nAlso, it **was** a minor change (based on impact). \r\n\r\n> Just if you want to do me a favour: make a new 4.X release which requires ruby2.2 or even 2.3, and make one last 3.X release which works with ruby1.9\r\n\r\nYou didn't read my reasons for doing what I did. And what's more important - you STILL didn't give me a compelling example of how I broke anything, really."}}