On Tue, Nov 19, 2013 at 8:43 PM, Tim Penhey tim.pen...@canonical.com wrote:
It was my understanding that the api server needs to be at least as
advanced as any client.
This means that a 1.18 server should be able to support a 1.16.x client.
However we don't support 1.18 clients on a 1.16.x
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-11-20 20:15, Curtis Hovey-Canonical wrote:
On Tue, Nov 19, 2013 at 8:43 PM, Tim Penhey
tim.pen...@canonical.com wrote:
It was my understanding that the api server needs to be at least
as advanced as any client.
This means that a 1.18
Hi everyone,
Though we have UDS sessions on Juju and charms all week I think it's
appropriate to share this one video as it covers the roadmap for Juju
for this cycle.
You can fast forward to 2:00 minute to get right to it:
- http://www.youtube.com/watch?v=ZjzImjEinB8feature=sharet=2m
--
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
John Arbash Meinel wrote:
I think that is one of the primary caveats for the we don't
guarantee all cross version compatibility is that we *do*
guarantee upgrade works.
I think we should also support status, so that
1. You can determine when an
I think that is a fair point. Especially right now when we haven't quite
nailed getting provider secrets on first connect.
John
=:-
On Nov 20, 2013 11:39 PM, Aaron Bentley aaron.bent...@canonical.com
wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
John Arbash Meinel wrote:
I think
