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.

Can 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.

WDYT guys?