Juju 1.17.5 is released

[Curtis Hovey-Canonical]

On Mon, Mar 17, 2014 at 5:01 AM, John Meinel <john at arbash-meinel.com> wrote:

>> I'm very happy to see this built, but we have a small problem with our
>> process. Specifically:
>>  1) the juju-1.17.5 client was created and published to the devel ppa
>>  2) before the jujud 1.17.5 tools were published to streams.canonical.com
>>  3) juju bootstrap is now lock-step, so 1.17.5 will refuse to
>> bootstrap anything but a 1.17.4 target
>>  4) PPAs don't keep a history, so anyone that gets the 1.17.5 binary
>> can't downgrade (easily) back to 1.17.4 until the tools are finally
>> available.

I am happy to read that juju now requires matching micro versions. I
wish this had been documented.Does this mean this bug is fixes
    https://bugs.launchpad.net/juju-core/+bug/1247232 [Juju client
deploys agent newer than itself]

The process assumes juju doesn't require a match.

Ben Howard made changes this morning to factor our the bus blocking
streams.canonical.com. As of this morning. when we the
lp:~juju-qa/juju-core/cd-release-juju branch is updates,
streams.canonical.com will automatically publish the tools.

However, we are still waiting for all the debs with the tools to be
built. Out PPA cannot build the new archs. WE must wait hours or days
for them the by built by ubuntu. This means that while new tools could
be published to CPCs with the the new archs. we must always wait for
ubuntu to build an publish for us to publish to streams.canonical.com.
Only after a potential long wait can be copy the new juju debs to the
public ppa.

We will do this to be safe, but we have given up a lot of control. No
person can make a release happen in a few hours. No person can ensure
one will happen in a day.



-- 
Curtis Hovey
Canonical Cloud Development and Operations
http://launchpad.net/~sinzui