Matt: Juju Core websocket API is going to be less intelligent in the long run. Practically, this means small things like being 100% specific when referring to charms, but the go branches themselves (new and old) will have to be wiped of any magic, and tests will have to be absolutely specific, involving a mocked charmstore, etc. Upgrade charm is a current example. Deploying a charm may be divided in the future. Deploy might be divided in the API into something like create service, set units, set charm.
Benji: we need to make sure that Juju Core has a versioning story that we can use.
Mark Ramm: yes, we have one, but it may still change.