Comment 3 for bug 1247232

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 2013-11-02 3:29, Dave Cheney wrote:
> On Sat, Nov 2, 2013 at 6:38 AM, Curtis Hovey <email address hidden>
> wrote:
>> We have an upgrade-juju --version=XXX command that explicitly
>> sets the version to be deployed, Users can use that now if they
>> wish. The bootstrap command also has options to select tools from
>> a series, but not version. I think then, that bootstrap should
>> only choose the same version as the client. the user can upgrade
>> if they wish, or upgrade- juju to just update the agents.
>
> This is a regression. Tools selection should only allow an exact
> match, ie, the client version and the initial agent version must
> match.

It is not a regression. We only require the Major.Minor version to
match. Not the Major.Minor.Patch level.

It is intentional that you could have a client and get a bugfixed
version of the agents. Note that the intention is that 1.16.2 will
always be 100% compatible with 1.16.0.

I'm pretty sure this is by design (and thus Won't Fix). If we want, we
could turn this into a request to be able to "juju bootstrap" with an
exact version of the tools.

John
=:->

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.13 (Cygwin)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlJ11GgACgkQJdeBCYSNAAOtOgCfTuAZnIvrUqK6IFzvomLKrK6l
qmEAoNaW0gr3m0ZLkOQww90S08b/9Iot
=uzWw
-----END PGP SIGNATURE-----