{"action":"opened","issue":{"url":"https://api.github.com/repos/doctrine/common/issues/704","labels_url":"https://api.github.com/repos/doctrine/common/issues/704/labels{/name}","comments_url":"https://api.github.com/repos/doctrine/common/issues/704/comments","events_url":"https://api.github.com/repos/doctrine/common/issues/704/events","html_url":"https://github.com/doctrine/common/issues/704","id":122514611,"number":704,"title":"2.5 => 2.6 why minor?","user":{"login":"rbalazs","id":1642641,"avatar_url":"https://avatars.githubusercontent.com/u/1642641?v=3","gravatar_id":"","url":"https://api.github.com/users/rbalazs","html_url":"https://github.com/rbalazs","followers_url":"https://api.github.com/users/rbalazs/followers","following_url":"https://api.github.com/users/rbalazs/following{/other_user}","gists_url":"https://api.github.com/users/rbalazs/gists{/gist_id}","starred_url":"https://api.github.com/users/rbalazs/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/rbalazs/subscriptions","organizations_url":"https://api.github.com/users/rbalazs/orgs","repos_url":"https://api.github.com/users/rbalazs/repos","events_url":"https://api.github.com/users/rbalazs/events{/privacy}","received_events_url":"https://api.github.com/users/rbalazs/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-12-16T14:24:02Z","updated_at":"2015-12-16T14:24:02Z","closed_at":null,"body":"The commit introduced code depending on a \"new\" language feature (Short Array Syntax / php 5.4), trivially breaking backward compatibility. The minor version bump is defendable, because it not about the doctrine API, rather about the legacy eco, but still, why not raise major (aka. breaking) version? It would have notified the package managers to avoid the new version, because it might break the existing system. I am curios about your opinion. Thank you for any help you can provide!"}}