{"action":"created","issue":{"url":"https://api.github.com/repos/GoogleCloudPlatform/google-cloud-php/issues/166","repository_url":"https://api.github.com/repos/GoogleCloudPlatform/google-cloud-php","labels_url":"https://api.github.com/repos/GoogleCloudPlatform/google-cloud-php/issues/166/labels{/name}","comments_url":"https://api.github.com/repos/GoogleCloudPlatform/google-cloud-php/issues/166/comments","events_url":"https://api.github.com/repos/GoogleCloudPlatform/google-cloud-php/issues/166/events","html_url":"https://github.com/GoogleCloudPlatform/google-cloud-php/issues/166","id":179344411,"number":166,"title":"We should separate composer packages","user":{"login":"tmatsuo","id":41815,"avatar_url":"https://avatars.githubusercontent.com/u/41815?v=3","gravatar_id":"","url":"https://api.github.com/users/tmatsuo","html_url":"https://github.com/tmatsuo","followers_url":"https://api.github.com/users/tmatsuo/followers","following_url":"https://api.github.com/users/tmatsuo/following{/other_user}","gists_url":"https://api.github.com/users/tmatsuo/gists{/gist_id}","starred_url":"https://api.github.com/users/tmatsuo/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/tmatsuo/subscriptions","organizations_url":"https://api.github.com/users/tmatsuo/orgs","repos_url":"https://api.github.com/users/tmatsuo/repos","events_url":"https://api.github.com/users/tmatsuo/events{/privacy}","received_events_url":"https://api.github.com/users/tmatsuo/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":4,"created_at":"2016-09-26T21:40:47Z","updated_at":"2016-09-27T13:51:31Z","closed_at":null,"body":"Now the composer package \"google/cloud\" contains all of the service client code. This is problematic when we think about semantic versioning. For example, when we release a new version of the API foobar, e.g. foobar v2.0.0 with incompatible changes, what should we do? If we conform to the semantic versioning, the only option is to change the major version of \"google/cloud\". I think it's problematic when we have many APIs to support.\r\n\r\nCan we revisit the decision of not having multiple github repos for releases? We can still continue using this central repo for development, issue tracking, PRs etc. We can leverage the github API for automation. We can disable issue tracking/PRs on the new release repos.\r\n\r\nWDYT guys?"},"comment":{"url":"https://api.github.com/repos/GoogleCloudPlatform/google-cloud-php/issues/comments/249870778","html_url":"https://github.com/GoogleCloudPlatform/google-cloud-php/issues/166#issuecomment-249870778","issue_url":"https://api.github.com/repos/GoogleCloudPlatform/google-cloud-php/issues/166","id":249870778,"user":{"login":"tmatsuo","id":41815,"avatar_url":"https://avatars.githubusercontent.com/u/41815?v=3","gravatar_id":"","url":"https://api.github.com/users/tmatsuo","html_url":"https://github.com/tmatsuo","followers_url":"https://api.github.com/users/tmatsuo/followers","following_url":"https://api.github.com/users/tmatsuo/following{/other_user}","gists_url":"https://api.github.com/users/tmatsuo/gists{/gist_id}","starred_url":"https://api.github.com/users/tmatsuo/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/tmatsuo/subscriptions","organizations_url":"https://api.github.com/users/tmatsuo/orgs","repos_url":"https://api.github.com/users/tmatsuo/repos","events_url":"https://api.github.com/users/tmatsuo/events{/privacy}","received_events_url":"https://api.github.com/users/tmatsuo/received_events","type":"User","site_admin":false},"created_at":"2016-09-27T13:51:31Z","updated_at":"2016-09-27T13:51:31Z","body":"One alternative approach to this problem is to propose a change to composer and packagist, basically allowing a single github repo have multiple composer packages on packagist. At a glance, this approach looks promising, but this proposal may take forever to take place. Here are the reasons; it is out of our control, there are bunch of stuff we need to consider, a mental barrier for breaking the current simplicity.\r\n\r\nSpeaking of the simplicity, the current 1:1 model gives a great simplicity around releasing PHP packages; a very handy integration of github release feature, a minimum UI on packagist, etc.\r\n\r\n I'm afraid it will unlikely be ready before we hit 1.0.\r\n\r\nMy splitting proposal can be done only within our side. I'd love to start a design document if we agree to do this. Also I can donate my time for the implementation.\r\n\r\nHow does it sound?"}}
{"actor":{"display_login":"tmatsuo"}}