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
-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
I am not sure if I am leading a discussion or just stating that we
have a problem that I don't believe can be ever solved.
We abandoned the release of 1.16.4 because we found it was
incompatible with 1.16.3
https://bugs.launchpad.net/juju-core/+bug/1252469
API incompatability: ERROR no
